Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 42376f4450095736cf6b0573fbce5f996c1c347d81b8a4700e93506c76973026

Tx prefix hash: 324d270f309ba948df2a58df3f56d1f798854138c5c0c005b22d82000edc9198
Tx public key: 0e696d4785fbd78a41675b5796b80d12b323fb422565e0b42e302cc639309b6f
Timestamp: 1737091476 Timestamp [UCT]: 2025-01-17 05:24:36 Age [y:d:h:m:s]: 00:151:21:05:07
Block: 1199106 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 108250 RingCT/type: yes/0
Extra: 010e696d4785fbd78a41675b5796b80d12b323fb422565e0b42e302cc639309b6f02110000000b007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 7d10584e76853f963908c8ea852e5ed3e7c5f185b9da00091abe48e9ae2b50c3 0.600000000000 1685735 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": 1199116, "vin": [ { "gen": { "height": 1199106 } } ], "vout": [ { "amount": 600000000, "target": { "key": "7d10584e76853f963908c8ea852e5ed3e7c5f185b9da00091abe48e9ae2b50c3" } } ], "extra": [ 1, 14, 105, 109, 71, 133, 251, 215, 138, 65, 103, 91, 87, 150, 184, 13, 18, 179, 35, 251, 66, 37, 101, 224, 180, 46, 48, 44, 198, 57, 48, 155, 111, 2, 17, 0, 0, 0, 11, 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