Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 7671a1548bdc098c1bbcf41e6123721d510ebb22795a1378c39719ce2d34d96a

Tx prefix hash: af720011af9dcda2fdd5761feeff7d53341b41f5cd2d40f5fc8777249a4c0b52
Tx public key: 3da6bdb9ff522d4da81bfccfdca36252ef3bb4be06a04154720ca46e6f4f17e1
Timestamp: 1723145791 Timestamp [UCT]: 2024-08-08 19:36:31 Age [y:d:h:m:s]: 00:244:17:01:31
Block: 1083630 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 174792 RingCT/type: yes/0
Extra: 013da6bdb9ff522d4da81bfccfdca36252ef3bb4be06a04154720ca46e6f4f17e1021100000007e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: b747c6bf690f284f0a4f213dc88bf403da549cc9f22f9a2a1efe28e2d3831c24 0.600000000000 1557619 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": 1083640, "vin": [ { "gen": { "height": 1083630 } } ], "vout": [ { "amount": 600000000, "target": { "key": "b747c6bf690f284f0a4f213dc88bf403da549cc9f22f9a2a1efe28e2d3831c24" } } ], "extra": [ 1, 61, 166, 189, 185, 255, 82, 45, 77, 168, 27, 252, 207, 220, 163, 98, 82, 239, 59, 180, 190, 6, 160, 65, 84, 114, 12, 164, 110, 111, 79, 23, 225, 2, 17, 0, 0, 0, 7, 233, 20, 221, 21, 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