Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: ff0323ec91597bc7da517949cd545f88c8f9f6a727cbd8fd0fbf5d9fe97cba56

Tx prefix hash: 9a5ab8542fc5f195864eb5b87d6ec44021dc89209c7d255d0924f6e66ac81859
Tx public key: dfab5936444ec539c8c6a22831aebdf9c7cf41ba0ddeaa3a55dd6fb60ddfe4a1
Timestamp: 1736879792 Timestamp [UCT]: 2025-01-14 18:36:32 Age [y:d:h:m:s]: 00:306:23:01:19
Block: 1197349 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 216888 RingCT/type: yes/0
Extra: 01dfab5936444ec539c8c6a22831aebdf9c7cf41ba0ddeaa3a55dd6fb60ddfe4a1021100000006007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: a4b2e7461d73e2b3debf3ac6e89adbe56d144a63265f49512d58b9238adc7ed4 0.600000000000 1683956 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": 1197359, "vin": [ { "gen": { "height": 1197349 } } ], "vout": [ { "amount": 600000000, "target": { "key": "a4b2e7461d73e2b3debf3ac6e89adbe56d144a63265f49512d58b9238adc7ed4" } } ], "extra": [ 1, 223, 171, 89, 54, 68, 78, 197, 57, 200, 198, 162, 40, 49, 174, 189, 249, 199, 207, 65, 186, 13, 222, 170, 58, 85, 221, 111, 182, 13, 223, 228, 161, 2, 17, 0, 0, 0, 6, 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