Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: b60b6cc46b9b0ff7b6ad2f4d4571c791b9cb2421713bc7f54d2eb15e9316cb6d

Tx prefix hash: 319d469dee673eb033a44bfb7a4298e63919b9e13a057c8d61e9d5b18eaca55c
Tx public key: 00584a0f6c518bc5f1ba60ef00fa262e468669442bea8c00c7d4d86e1258380e
Timestamp: 1739153310 Timestamp [UCT]: 2025-02-10 02:08:30 Age [y:d:h:m:s]: 00:351:23:31:45
Block: 1215902 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 249239 RingCT/type: yes/0
Extra: 0100584a0f6c518bc5f1ba60ef00fa262e468669442bea8c00c7d4d86e1258380e021100000003007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 7471e8c8a5437b5d0a3b4c83e6c59e212cf51232b29edea40953d79b29c6ebff 0.600000000000 1702701 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": 1215912, "vin": [ { "gen": { "height": 1215902 } } ], "vout": [ { "amount": 600000000, "target": { "key": "7471e8c8a5437b5d0a3b4c83e6c59e212cf51232b29edea40953d79b29c6ebff" } } ], "extra": [ 1, 0, 88, 74, 15, 108, 81, 139, 197, 241, 186, 96, 239, 0, 250, 38, 46, 70, 134, 105, 68, 43, 234, 140, 0, 199, 212, 216, 110, 18, 88, 56, 14, 2, 17, 0, 0, 0, 3, 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