Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 31043a158fd2ae282a715aa43707cd50727e7e52613e5e1567be15ad7beb6122

Tx prefix hash: 45e7a68c7d3676d44424cbc3bec99b719d3edc14d1112ba8f21fb8dc2f9ed112
Tx public key: eb2a1dbb0c6c11924c4729cf8c37bff163e7ced6435d4aa96ca14dbd70e3bcdd
Timestamp: 1708007403 Timestamp [UCT]: 2024-02-15 14:30:03 Age [y:d:h:m:s]: 01:011:02:38:00
Block: 958127 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 268945 RingCT/type: yes/0
Extra: 01eb2a1dbb0c6c11924c4729cf8c37bff163e7ced6435d4aa96ca14dbd70e3bcdd02110000000259dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: dcc7ebd9249060cb98ec53116ac9a41b6c58962bf718ebf4ab8dca88ac9650a0 0.600000000000 1417480 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": 958137, "vin": [ { "gen": { "height": 958127 } } ], "vout": [ { "amount": 600000000, "target": { "key": "dcc7ebd9249060cb98ec53116ac9a41b6c58962bf718ebf4ab8dca88ac9650a0" } } ], "extra": [ 1, 235, 42, 29, 187, 12, 108, 17, 146, 76, 71, 41, 207, 140, 55, 191, 241, 99, 231, 206, 214, 67, 93, 74, 169, 108, 161, 77, 189, 112, 227, 188, 221, 2, 17, 0, 0, 0, 2, 89, 218, 211, 245, 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