Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: b36b1b68d30933fde5e49f68b156865c07fb36660ed3c95015c35d3cf1982b8f

Tx prefix hash: abc4d52dc3f320ca039511ee3534c052b34d736cd9cdeb953a72fab19c08255e
Tx public key: 938d0f38d870d5a125ffc27b0c32e16039e931beedc8d6ba65bc4e10b9534969
Timestamp: 1746361855 Timestamp [UCT]: 2025-05-04 12:30:55 Age [y:d:h:m:s]: 00:201:10:41:20
Block: 1275582 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 141686 RingCT/type: yes/0
Extra: 01938d0f38d870d5a125ffc27b0c32e16039e931beedc8d6ba65bc4e10b95349690211000000021f90517a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: a7cc8392f1f7da0a4e7a1bfed17cafc65634a8e3cd2e5ea5ca4e3a5b385464a3 0.600000000000 1762897 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": 1275592, "vin": [ { "gen": { "height": 1275582 } } ], "vout": [ { "amount": 600000000, "target": { "key": "a7cc8392f1f7da0a4e7a1bfed17cafc65634a8e3cd2e5ea5ca4e3a5b385464a3" } } ], "extra": [ 1, 147, 141, 15, 56, 216, 112, 213, 161, 37, 255, 194, 123, 12, 50, 225, 96, 57, 233, 49, 190, 237, 200, 214, 186, 101, 188, 78, 16, 185, 83, 73, 105, 2, 17, 0, 0, 0, 2, 31, 144, 81, 122, 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