Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 0c9aec6a3346c96fb09917f03161e057b8a0ddea7973210b4b360025c1107528

Tx prefix hash: fe97bc2cd96a50474bbe029d821c6060dcecba589846508878ba589cfc00fb9f
Tx public key: a05897ee3ee9e29391e4c3f89c6276148937ce18f48d42510100d2d7ca81d103
Timestamp: 1627643870 Timestamp [UCT]: 2021-07-30 11:17:50 Age [y:d:h:m:s]: 03:193:08:48:21
Block: 303817 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 910489 RingCT/type: yes/0
Extra: 01a05897ee3ee9e29391e4c3f89c6276148937ce18f48d42510100d2d7ca81d10302110000001701f1e57f000000000000000000

1 output(s) for total of 60.440582811000 dcy

stealth address amount amount idx
00: 8d2d2661271694e3233b13b53858d88b7f5e665207dc53396feef388e996ae12 60.440582811000 634060 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": 303827, "vin": [ { "gen": { "height": 303817 } } ], "vout": [ { "amount": 60440582811, "target": { "key": "8d2d2661271694e3233b13b53858d88b7f5e665207dc53396feef388e996ae12" } } ], "extra": [ 1, 160, 88, 151, 238, 62, 233, 226, 147, 145, 228, 195, 248, 156, 98, 118, 20, 137, 55, 206, 24, 244, 141, 66, 81, 1, 0, 210, 215, 202, 129, 209, 3, 2, 17, 0, 0, 0, 23, 1, 241, 229, 127, 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