Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 77ec10e2594ca261fa833296e96ee806460e53198e542fe0e054e27386b15df3

Tx prefix hash: 722aed442f45bcee8183b2692fee497a3778cd822873c93db397499f816e16b3
Tx public key: d83aff0872bf3b3700b8133f28a2ef1fe9dccb60c1b422fe4d905e2defa95d10
Timestamp: 1710675479 Timestamp [UCT]: 2024-03-17 11:37:59 Age [y:d:h:m:s]: 01:013:13:23:27
Block: 980268 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 270652 RingCT/type: yes/0
Extra: 01d83aff0872bf3b3700b8133f28a2ef1fe9dccb60c1b422fe4d905e2defa95d100211000000027a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 6ad952fb7d240e207e5efc528f02be980b4aefebd7a89be74cdc0d4d38a5ebcf 0.600000000000 1440333 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": 980278, "vin": [ { "gen": { "height": 980268 } } ], "vout": [ { "amount": 600000000, "target": { "key": "6ad952fb7d240e207e5efc528f02be980b4aefebd7a89be74cdc0d4d38a5ebcf" } } ], "extra": [ 1, 216, 58, 255, 8, 114, 191, 59, 55, 0, 184, 19, 63, 40, 162, 239, 31, 233, 220, 203, 96, 193, 180, 34, 254, 77, 144, 94, 45, 239, 169, 93, 16, 2, 17, 0, 0, 0, 2, 122, 156, 244, 199, 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