Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: afc2110aabdc87cceee121504139008c622de43afe9d4ae9a06418f560ef16ff

Tx prefix hash: e98e2166e7748beee03eb6c12d2653992a6f1cc04ad3ff2b4cb064032c0dc70b
Tx public key: 0f1caa207214f38820e4e9a4e2cb1dc5a0ec1293e4c9cf4cdfec8df969a021e4
Timestamp: 1708959600 Timestamp [UCT]: 2024-02-26 15:00:00 Age [y:d:h:m:s]: 01:267:17:01:29
Block: 966029 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 450076 RingCT/type: yes/0
Extra: 010f1caa207214f38820e4e9a4e2cb1dc5a0ec1293e4c9cf4cdfec8df969a021e40211000000037a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: a4b2fdfc74c852bf5aaa5738cdb6d294e3553d10748e4c368d97e8e6415a7be3 0.600000000000 1425786 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": 966039, "vin": [ { "gen": { "height": 966029 } } ], "vout": [ { "amount": 600000000, "target": { "key": "a4b2fdfc74c852bf5aaa5738cdb6d294e3553d10748e4c368d97e8e6415a7be3" } } ], "extra": [ 1, 15, 28, 170, 32, 114, 20, 243, 136, 32, 228, 233, 164, 226, 203, 29, 197, 160, 236, 18, 147, 228, 201, 207, 76, 223, 236, 141, 249, 105, 160, 33, 228, 2, 17, 0, 0, 0, 3, 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