Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: d55120de0f365b4b29424308055bd729d7da712a217e60bb33794c17ae6dcafe

Tx prefix hash: 6db0353de59ae2584ff488a268c5cdc4074cfa46cd7434714faf96f68b58099b
Tx public key: 070a8f41dc939c9142fb753c1434f084c6979193d21d37732b85502ebd735c5f
Timestamp: 1699697722 Timestamp [UCT]: 2023-11-11 10:15:22 Age [y:d:h:m:s]: 01:203:12:55:17
Block: 889250 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 406689 RingCT/type: yes/0
Extra: 01070a8f41dc939c9142fb753c1434f084c6979193d21d37732b85502ebd735c5f021100000004faf35c9c000000000000000000

1 output(s) for total of 0.694297504000 dcy

stealth address amount amount idx
00: f1b1981456dab9df81f33a5caf0880a021331c8efd3638eae627532a1e7d8bea 0.694297504000 1345231 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": 889260, "vin": [ { "gen": { "height": 889250 } } ], "vout": [ { "amount": 694297504, "target": { "key": "f1b1981456dab9df81f33a5caf0880a021331c8efd3638eae627532a1e7d8bea" } } ], "extra": [ 1, 7, 10, 143, 65, 220, 147, 156, 145, 66, 251, 117, 60, 20, 52, 240, 132, 198, 151, 145, 147, 210, 29, 55, 115, 43, 133, 80, 46, 189, 115, 92, 95, 2, 17, 0, 0, 0, 4, 250, 243, 92, 156, 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