Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 1861e4f2bcfa1f2434ee7e542cb184600e85416f7c9d6c2b5019776504883f7f

Tx prefix hash: 6a9830b5504156abf24e75deec3d0c134af0a309c200cc919b8d773eb671f1c3
Tx public key: 38bbeb40f0b6a0f74ccc7f302b7bf7544f7adc0971cb46fce91678174e967994
Timestamp: 1720010346 Timestamp [UCT]: 2024-07-03 12:39:06 Age [y:d:h:m:s]: 00:316:09:31:24
Block: 1057642 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 226092 RingCT/type: yes/0
Extra: 0138bbeb40f0b6a0f74ccc7f302b7bf7544f7adc0971cb46fce91678174e9679940211000000030011055b000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 14ff6d83d38d5df31feec0daff2072f7ad50ae9c4193dec39d9737699af6d816 0.600000000000 1528079 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": 1057652, "vin": [ { "gen": { "height": 1057642 } } ], "vout": [ { "amount": 600000000, "target": { "key": "14ff6d83d38d5df31feec0daff2072f7ad50ae9c4193dec39d9737699af6d816" } } ], "extra": [ 1, 56, 187, 235, 64, 240, 182, 160, 247, 76, 204, 127, 48, 43, 123, 247, 84, 79, 122, 220, 9, 113, 203, 70, 252, 233, 22, 120, 23, 78, 150, 121, 148, 2, 17, 0, 0, 0, 3, 0, 17, 5, 91, 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