Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 8d35b25949a5ffeec133c3c7ddb698841ce61de17c60cbea43a1b3d7553bb810

Tx prefix hash: c4b0afd7c24a4a36b56217347856e61a303abf113cf0aef896b515d6d31e402c
Tx public key: 8a083d7ada67f1582d23a01c02787ca8d1d8bfe8a7a37a1fdd13a0e0478b295c
Timestamp: 1736650043 Timestamp [UCT]: 2025-01-12 02:47:23 Age [y:d:h:m:s]: 00:157:23:25:31
Block: 1195442 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 112598 RingCT/type: yes/0
Extra: 018a083d7ada67f1582d23a01c02787ca8d1d8bfe8a7a37a1fdd13a0e0478b295c0211000000021f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: cc21c4d450aea4f698ab1d81ac8584e7524fb2eb49a816553b93ca2fff9d027b 0.600000000000 1682033 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": 1195452, "vin": [ { "gen": { "height": 1195442 } } ], "vout": [ { "amount": 600000000, "target": { "key": "cc21c4d450aea4f698ab1d81ac8584e7524fb2eb49a816553b93ca2fff9d027b" } } ], "extra": [ 1, 138, 8, 61, 122, 218, 103, 241, 88, 45, 35, 160, 28, 2, 120, 124, 168, 209, 216, 191, 232, 167, 163, 122, 31, 221, 19, 160, 224, 71, 139, 41, 92, 2, 17, 0, 0, 0, 2, 31, 10, 83, 235, 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