Dinastycoin Blockchain Explorer

(no javascript - no cookies - no web analytics trackers - no images - open sourced)

Autorefresh is OFF

Tx hash: e96681e3b894547145227fccec72a70fc4def68af0c640e9b516fdfd0614836f

Tx prefix hash: cf8859d2d29f2b160a13bf25cd27f76e410b4b2f7374dc78915a79e13f1a5567
Tx public key: 6b82245b6cb61739785993ff480a14a798dc335235dcd19f871c27ba19d281e5
Timestamp: 1737415073 Timestamp [UCT]: 2025-01-20 23:17:53 Age [y:d:h:m:s]: 00:147:23:33:24
Block: 1201744 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 105499 RingCT/type: yes/0
Extra: 016b82245b6cb61739785993ff480a14a798dc335235dcd19f871c27ba19d281e50211000000091f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 430b0c3e544bd9a219a55b0a3b9c4476d8ab874511f27664c79f271792f03c83 0.600000000000 1688401 of 15

Check which outputs belong to given Dinastycoin address/subaddress and viewkey

For RingCT transactions, outputs' amounts are also decoded
Note: address/subaddress and viewkey are sent to the server, as the calculations are done on the server side



Prove to someone that you have sent them Dinastycoin in this transaction

Tx private key can be obtained using get_tx_key command in dinasty-wallet-cli command line tool
Note: address/subaddress and tx private key are sent to the server, as the calculations are done on the server side



{ "version": 2, "unlock_time": 1201754, "vin": [ { "gen": { "height": 1201744 } } ], "vout": [ { "amount": 600000000, "target": { "key": "430b0c3e544bd9a219a55b0a3b9c4476d8ab874511f27664c79f271792f03c83" } } ], "extra": [ 1, 107, 130, 36, 91, 108, 182, 23, 57, 120, 89, 147, 255, 72, 10, 20, 167, 152, 220, 51, 82, 53, 220, 209, 159, 135, 28, 39, 186, 25, 210, 129, 229, 2, 17, 0, 0, 0, 9, 31, 10, 83, 235, 0, 0, 0, 0, 0, 0, 0, 0, 0 ], "rct_signatures": { "type": 0 } }


Less details
source code | explorer version (api): master-2022-04-20-3036769 (1.2) | dinastycoin version: 4.1-b41cfa2b8