Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: c03699b9c30e8b1cd3d4edd274bd6e6ae3830838661b127fb59d693a5ac6e47e

Tx prefix hash: 1635fc79269906530b373965fc8ac6d67845f1aa2631efb795ca15bd7dac9fc5
Tx public key: 6dced954baa8475ec70993b8c821fe6f81fd5ddef9a1c96f5be0f798b9d38fc8
Timestamp: 1741095916 Timestamp [UCT]: 2025-03-04 13:45:16 Age [y:d:h:m:s]: 00:261:11:52:16
Block: 1231996 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 184621 RingCT/type: yes/0
Extra: 016dced954baa8475ec70993b8c821fe6f81fd5ddef9a1c96f5be0f798b9d38fc8021100000006007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: d5ee448ca026058402bd674c48c577e9db447fd9d341cdf2461347874348edc6 0.600000000000 1718907 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": 1232006, "vin": [ { "gen": { "height": 1231996 } } ], "vout": [ { "amount": 600000000, "target": { "key": "d5ee448ca026058402bd674c48c577e9db447fd9d341cdf2461347874348edc6" } } ], "extra": [ 1, 109, 206, 217, 84, 186, 168, 71, 94, 199, 9, 147, 184, 200, 33, 254, 111, 129, 253, 93, 222, 249, 161, 201, 111, 91, 224, 247, 152, 185, 211, 143, 200, 2, 17, 0, 0, 0, 6, 0, 127, 151, 138, 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