Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 85dde7fbcc020f2b3b80ecfb58901808fce9fc92054a5aeb76d436208b4c7eed

Tx prefix hash: 4c6a8d2bb929bca1c53f9c56ad4c3522637c7a874677b9b921d955a65b5697ec
Tx public key: a8f080ead89d6a6788041ecffba01a47dc0363de4a7d16c82b8196cfdc3ecc10
Timestamp: 1720680618 Timestamp [UCT]: 2024-07-11 06:50:18 Age [y:d:h:m:s]: 00:273:15:59:35
Block: 1063205 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 195513 RingCT/type: yes/0
Extra: 01a8f080ead89d6a6788041ecffba01a47dc0363de4a7d16c82b8196cfdc3ecc10021100000001e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 519934253571aa37101522be018b82bc591740cf3c27dcf03e7f5c3c39cb606e 0.600000000000 1533720 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": 1063215, "vin": [ { "gen": { "height": 1063205 } } ], "vout": [ { "amount": 600000000, "target": { "key": "519934253571aa37101522be018b82bc591740cf3c27dcf03e7f5c3c39cb606e" } } ], "extra": [ 1, 168, 240, 128, 234, 216, 157, 106, 103, 136, 4, 30, 207, 251, 160, 26, 71, 220, 3, 99, 222, 74, 125, 22, 200, 43, 129, 150, 207, 220, 62, 204, 16, 2, 17, 0, 0, 0, 1, 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