Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: cc5dda8853a73c19c0f03eb789bf510e20034b4c9a97976f13a2e46ff6605601

Tx prefix hash: 61a96a10d1c8ea495ddf47229bb07d5e7ac9245b1c87351e9725c1f536a59913
Tx public key: c6465195f316643b3c3636897ee33b3fe7cde9a8a870546b90c61a587860e3e9
Timestamp: 1686129993 Timestamp [UCT]: 2023-06-07 09:26:33 Age [y:d:h:m:s]: 01:217:19:26:20
Block: 777005 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 417076 RingCT/type: yes/0
Extra: 01c6465195f316643b3c3636897ee33b3fe7cde9a8a870546b90c61a587860e3e902110000000233af99f4000000000000000000

1 output(s) for total of 1.634782758000 dcy

stealth address amount amount idx
00: 24bc57cef6460d9a9a3c8f596fc7bd2425d69f23991b0b944cffdd580ad1b3c7 1.634782758000 1226578 of 0

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": 777015, "vin": [ { "gen": { "height": 777005 } } ], "vout": [ { "amount": 1634782758, "target": { "key": "24bc57cef6460d9a9a3c8f596fc7bd2425d69f23991b0b944cffdd580ad1b3c7" } } ], "extra": [ 1, 198, 70, 81, 149, 243, 22, 100, 59, 60, 54, 54, 137, 126, 227, 59, 63, 231, 205, 233, 168, 168, 112, 84, 107, 144, 198, 26, 88, 120, 96, 227, 233, 2, 17, 0, 0, 0, 2, 51, 175, 153, 244, 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