Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 7c2ab006c13884eb9b77e0f07a0bdf535cc42dcf9c23d9bf59fec33a0eaa83f9

Tx prefix hash: 923148cb9d0406473cef67e5f45dd28cb0ad7ca7d7353aa47e2d016820b2744b
Tx public key: 77c6323bc5c11430dd87b0924b1f8c8ebecc01599e8261449d228806e8a108b9
Timestamp: 1709498211 Timestamp [UCT]: 2024-03-03 20:36:51 Age [y:d:h:m:s]: 01:081:00:33:32
Block: 970500 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 318941 RingCT/type: yes/0
Extra: 0177c6323bc5c11430dd87b0924b1f8c8ebecc01599e8261449d228806e8a108b90211000000060011055b000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: ea86c10d09ba6fc6b00737e08d1f701a32fea125eff933efb570bcdfd6a51bfd 0.600000000000 1430357 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": 970510, "vin": [ { "gen": { "height": 970500 } } ], "vout": [ { "amount": 600000000, "target": { "key": "ea86c10d09ba6fc6b00737e08d1f701a32fea125eff933efb570bcdfd6a51bfd" } } ], "extra": [ 1, 119, 198, 50, 59, 197, 193, 20, 48, 221, 135, 176, 146, 75, 31, 140, 142, 190, 204, 1, 89, 158, 130, 97, 68, 157, 34, 136, 6, 232, 161, 8, 185, 2, 17, 0, 0, 0, 6, 0, 17, 5, 91, 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