Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: a18669279f8b6e62caf43a7682fb9fc594ea12834443fb8be0fc0af2fc227b6e

Tx prefix hash: b94453b80ad7c0691aa938e877d6ee672d974bb252dfca47aa317426777e5110
Tx public key: 5e924c45d4006d2777e6f28ffbaecae8b3c95ffc7a07efd4dcf03a295241cd6e
Timestamp: 1724073581 Timestamp [UCT]: 2024-08-19 13:19:41 Age [y:d:h:m:s]: 00:297:22:14:01
Block: 1091334 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 212778 RingCT/type: yes/0
Extra: 015e924c45d4006d2777e6f28ffbaecae8b3c95ffc7a07efd4dcf03a295241cd6e02110000000191e13c04000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 6de3011c1265a6ca2bb810781107bbe13f6ea2c76bb0be877014d8f699261293 0.600000000000 1565965 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": 1091344, "vin": [ { "gen": { "height": 1091334 } } ], "vout": [ { "amount": 600000000, "target": { "key": "6de3011c1265a6ca2bb810781107bbe13f6ea2c76bb0be877014d8f699261293" } } ], "extra": [ 1, 94, 146, 76, 69, 212, 0, 109, 39, 119, 230, 242, 143, 251, 174, 202, 232, 179, 201, 95, 252, 122, 7, 239, 212, 220, 240, 58, 41, 82, 65, 205, 110, 2, 17, 0, 0, 0, 1, 145, 225, 60, 4, 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