Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 6609b5992fe1c2cc6f3fa2a580bde0c40db2d630cbb83572aaf05b8768f169b2

Tx prefix hash: 9deb3cd5782c63998245809bc7c9c914074f3638d7c9942f86fcb1b01d925d6d
Tx public key: 0a8d8b28d03e757d322ab5f8dda304a28ad60bdaa1ccab5ebd310ec057857d09
Timestamp: 1634639224 Timestamp [UCT]: 2021-10-19 10:27:04 Age [y:d:h:m:s]: 03:031:14:18:46
Block: 356114 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 800650 RingCT/type: yes/0
Extra: 010a8d8b28d03e757d322ab5f8dda304a28ad60bdaa1ccab5ebd310ec057857d0902110000004b36fe6557000000000000000000

1 output(s) for total of 40.556383169000 dcy

stealth address amount amount idx
00: 15626bfda367a617084064b25a368d913efa82ee3963d3a7e5a73deb9a9f66e1 40.556383169000 726722 of 0

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": 356124, "vin": [ { "gen": { "height": 356114 } } ], "vout": [ { "amount": 40556383169, "target": { "key": "15626bfda367a617084064b25a368d913efa82ee3963d3a7e5a73deb9a9f66e1" } } ], "extra": [ 1, 10, 141, 139, 40, 208, 62, 117, 125, 50, 42, 181, 248, 221, 163, 4, 162, 138, 214, 11, 218, 161, 204, 171, 94, 189, 49, 14, 192, 87, 133, 125, 9, 2, 17, 0, 0, 0, 75, 54, 254, 101, 87, 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