Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 19251ca843b0b5138010866182d0dfc1bc171b26e79177af6aa7173108040ae7

Tx prefix hash: dc3c9e50fa887f7696451588f99c849a08d6df7d90d16dcffd30a62915d9e8e2
Tx public key: a3c7009f42d61bbca58d175f1670eee50a9cbac1e7ef3dbea563941f19369ae0
Timestamp: 1735212149 Timestamp [UCT]: 2024-12-26 11:22:29 Age [y:d:h:m:s]: 00:089:14:46:31
Block: 1183557 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 63809 RingCT/type: yes/0
Extra: 01a3c7009f42d61bbca58d175f1670eee50a9cbac1e7ef3dbea563941f19369ae0021100000002007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: ea4e307a3c995d34e6f3a9af25634d12abd068a964caa922445eb87ef6ef5371 0.600000000000 1670002 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": 1183567, "vin": [ { "gen": { "height": 1183557 } } ], "vout": [ { "amount": 600000000, "target": { "key": "ea4e307a3c995d34e6f3a9af25634d12abd068a964caa922445eb87ef6ef5371" } } ], "extra": [ 1, 163, 199, 0, 159, 66, 214, 27, 188, 165, 141, 23, 95, 22, 112, 238, 229, 10, 156, 186, 193, 231, 239, 61, 190, 165, 99, 148, 31, 25, 54, 154, 224, 2, 17, 0, 0, 0, 2, 0, 127, 151, 138, 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