Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 624e8d7a229d4846412090142e9c218b48d15a001e42688c71ed97e6bd8a2f8f

Tx prefix hash: 0af1649bbd01218d1865aab8477d7d539bb2053fc1d55f71afeced367baa136d
Tx public key: d2d992cf87ba2ecaf93e616194bf6a984c6bfb1b72beac7063e82c2ca41fa27e
Timestamp: 1696733142 Timestamp [UCT]: 2023-10-08 02:45:42 Age [y:d:h:m:s]: 01:248:10:40:48
Block: 864869 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 438600 RingCT/type: yes/0
Extra: 01d2d992cf87ba2ecaf93e616194bf6a984c6bfb1b72beac7063e82c2ca41fa27e021100000002bfa22221000000000000000000

1 output(s) for total of 0.836238221000 dcy

stealth address amount amount idx
00: 17abd20a1bb92bb3027e9bc49664162271b7eab62e50a3cb3b038882a3c05e6a 0.836238221000 1319391 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": 864879, "vin": [ { "gen": { "height": 864869 } } ], "vout": [ { "amount": 836238221, "target": { "key": "17abd20a1bb92bb3027e9bc49664162271b7eab62e50a3cb3b038882a3c05e6a" } } ], "extra": [ 1, 210, 217, 146, 207, 135, 186, 46, 202, 249, 62, 97, 97, 148, 191, 106, 152, 76, 107, 251, 27, 114, 190, 172, 112, 99, 232, 44, 44, 164, 31, 162, 126, 2, 17, 0, 0, 0, 2, 191, 162, 34, 33, 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