Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: e9a9501b2b04bfd7953693fa38fb213495c9619f111f63ae7366184641da9821

Tx prefix hash: c55ab96c12507961d72a3e502de4d4b1da52f7bc0ccf8bf7d45f55d9ad8629cc
Tx public key: 5b3a8a8316edd29d3a16d9be64ab6072aec686d4eedba403f1ee24b21d5656bf
Timestamp: 1578915873 Timestamp [UCT]: 2020-01-13 11:44:33 Age [y:d:h:m:s]: 04:361:18:18:34
Block: 44543 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1148141 RingCT/type: yes/0
Extra: 015b3a8a8316edd29d3a16d9be64ab6072aec686d4eedba403f1ee24b21d5656bf0211000000bf17786bcf000000000000000000

1 output(s) for total of 436.929523649000 dcy

stealth address amount amount idx
00: 2ed49b64b25ae788ddd54648c8d9bbe653bbc1cfd609e358265efb939d1195dc 436.929523649000 81084 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": 44553, "vin": [ { "gen": { "height": 44543 } } ], "vout": [ { "amount": 436929523649, "target": { "key": "2ed49b64b25ae788ddd54648c8d9bbe653bbc1cfd609e358265efb939d1195dc" } } ], "extra": [ 1, 91, 58, 138, 131, 22, 237, 210, 157, 58, 22, 217, 190, 100, 171, 96, 114, 174, 198, 134, 212, 238, 219, 164, 3, 241, 238, 36, 178, 29, 86, 86, 191, 2, 17, 0, 0, 0, 191, 23, 120, 107, 207, 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