Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: f905af16ecf6eb4cb77e6110e3451751ce93c5cddcf4d76d87178124a9d716f2

Tx prefix hash: d17dca4434b497e01f709daddd982afca1d47faf5bfdbe61598d32338c259ea9
Tx public key: 264d9ea453274fa0e737e58c85ae9a2dcafc4e2699c4abb3969ca1dd8eb29431
Timestamp: 1635248595 Timestamp [UCT]: 2021-10-26 11:43:15 Age [y:d:h:m:s]: 03:011:02:57:24
Block: 360884 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 786261 RingCT/type: yes/0
Extra: 01264d9ea453274fa0e737e58c85ae9a2dcafc4e2699c4abb3969ca1dd8eb294310211000000154f792ffd000000000000000000

1 output(s) for total of 39.105865800000 dcy

stealth address amount amount idx
00: 464e7b911ab734c6a8fe99ec3af9bddfddd12ae296c8d226420f6643f8dcfcdd 39.105865800000 734387 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": 360894, "vin": [ { "gen": { "height": 360884 } } ], "vout": [ { "amount": 39105865800, "target": { "key": "464e7b911ab734c6a8fe99ec3af9bddfddd12ae296c8d226420f6643f8dcfcdd" } } ], "extra": [ 1, 38, 77, 158, 164, 83, 39, 79, 160, 231, 55, 229, 140, 133, 174, 154, 45, 202, 252, 78, 38, 153, 196, 171, 179, 150, 156, 161, 221, 142, 178, 148, 49, 2, 17, 0, 0, 0, 21, 79, 121, 47, 253, 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