Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 9d17c022a9e6503dc7c1c97a3303b8d7825a1471933114099b76b7bdcf68ea9b

Tx prefix hash: a38025c75498ba372d53b09e99c5057552854f2e2bef87f0cafee6d0b03834f3
Tx public key: 4ea984d67d4ae36306662613eaa26e06c806e43b0db464188d5cf8c6708756cb
Timestamp: 1706710569 Timestamp [UCT]: 2024-01-31 14:16:09 Age [y:d:h:m:s]: 00:288:09:58:27
Block: 947359 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 206531 RingCT/type: yes/0
Extra: 014ea984d67d4ae36306662613eaa26e06c806e43b0db464188d5cf8c6708756cb021100000001c5452960000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 0e557a4e0f827ea664aefc177f5de25a25c53d8dcd0b195200ca9ab19164da7a 0.600000000000 1405707 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": 947369, "vin": [ { "gen": { "height": 947359 } } ], "vout": [ { "amount": 600000000, "target": { "key": "0e557a4e0f827ea664aefc177f5de25a25c53d8dcd0b195200ca9ab19164da7a" } } ], "extra": [ 1, 78, 169, 132, 214, 125, 74, 227, 99, 6, 102, 38, 19, 234, 162, 110, 6, 200, 6, 228, 59, 13, 180, 100, 24, 141, 92, 248, 198, 112, 135, 86, 203, 2, 17, 0, 0, 0, 1, 197, 69, 41, 96, 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