Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 50e2b119c721a55ec6704e21b02d7eb62db817fe5307785f1cd0370460960448

Tx prefix hash: b8e6be6721093ddb525bc13b72ca5c67c9546c3c61a1afd36ab9a73af5416a46
Tx public key: 6a872c7742bbd3da3812daae473351b972d859a35ea04a406992030b528ddae0
Timestamp: 1727950694 Timestamp [UCT]: 2024-10-03 10:18:14 Age [y:d:h:m:s]: 00:225:04:26:48
Block: 1123476 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 160763 RingCT/type: yes/0
Extra: 016a872c7742bbd3da3812daae473351b972d859a35ea04a406992030b528ddae002110000000391e13c04000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 1f13fb6ebeb55bb2c230e2f9e12e066c0a5568d35213fd246f9e5cb039acec2f 0.600000000000 1606011 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": 1123486, "vin": [ { "gen": { "height": 1123476 } } ], "vout": [ { "amount": 600000000, "target": { "key": "1f13fb6ebeb55bb2c230e2f9e12e066c0a5568d35213fd246f9e5cb039acec2f" } } ], "extra": [ 1, 106, 135, 44, 119, 66, 187, 211, 218, 56, 18, 218, 174, 71, 51, 81, 185, 114, 216, 89, 163, 94, 160, 74, 64, 105, 146, 3, 11, 82, 141, 218, 224, 2, 17, 0, 0, 0, 3, 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