Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 702e0e595ab57a5cb44128139c3e6fbfb7781a488f28e282910799ce3b240e6c

Tx prefix hash: 4a48183c1437d4127dd8f392e75a3062e94e78571ef932102e9871e02815448e
Tx public key: f3abe5b901ff7b3ea737e8cc89e3f5c71d90bb431c7ed6426a3d4dbe2c8b8a84
Timestamp: 1727019903 Timestamp [UCT]: 2024-09-22 15:45:03 Age [y:d:h:m:s]: 00:199:06:33:00
Block: 1115756 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 142231 RingCT/type: yes/0
Extra: 01f3abe5b901ff7b3ea737e8cc89e3f5c71d90bb431c7ed6426a3d4dbe2c8b8a8402110000000491e13c04000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: d9a305863657d1ad53091fefa3333702703a394cfdf75dc0b9877690ccb61c7c 0.600000000000 1595997 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": 1115766, "vin": [ { "gen": { "height": 1115756 } } ], "vout": [ { "amount": 600000000, "target": { "key": "d9a305863657d1ad53091fefa3333702703a394cfdf75dc0b9877690ccb61c7c" } } ], "extra": [ 1, 243, 171, 229, 185, 1, 255, 123, 62, 167, 55, 232, 204, 137, 227, 245, 199, 29, 144, 187, 67, 28, 126, 214, 66, 106, 61, 77, 190, 44, 139, 138, 132, 2, 17, 0, 0, 0, 4, 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