Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 1c6a52a363b1889858e24eafa2c504eef1447891a1d6c81dd2e00f61d5315955

Tx prefix hash: 37c087dca722a89f511021f2ce136049f15cb3b2062cb0c470e9e12a54706db2
Tx public key: a62cbfe36209e885a502d5717bd0559fd66c0d90c0b65681ffe23fd18fe9f3e7
Timestamp: 1716275839 Timestamp [UCT]: 2024-05-21 07:17:19 Age [y:d:h:m:s]: 00:305:15:43:11
Block: 1026690 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 218461 RingCT/type: yes/0
Extra: 01a62cbfe36209e885a502d5717bd0559fd66c0d90c0b65681ffe23fd18fe9f3e702110000000152d47e94000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 39dd8957c090b1bc937974b8d7934bcb1a31a3688bac1c23bbb3f3bccabe2ee4 0.600000000000 1493911 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": 1026700, "vin": [ { "gen": { "height": 1026690 } } ], "vout": [ { "amount": 600000000, "target": { "key": "39dd8957c090b1bc937974b8d7934bcb1a31a3688bac1c23bbb3f3bccabe2ee4" } } ], "extra": [ 1, 166, 44, 191, 227, 98, 9, 232, 133, 165, 2, 213, 113, 123, 208, 85, 159, 214, 108, 13, 144, 192, 182, 86, 129, 255, 226, 63, 209, 143, 233, 243, 231, 2, 17, 0, 0, 0, 1, 82, 212, 126, 148, 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