Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: a46c9a49feec7d73ebe7df4edc6bcc523887355fc7e2fd1e4eec7e02b896aa9e

Tx prefix hash: ccd069b6544b8bfc3faf6b9c888943ad91d1234fdb45e58bee9627f0001811b7
Tx public key: 3f35cdfde2ebcd276be5fcbeb97255f8e0216c2d066f743b9167e2ed0c235beb
Timestamp: 1767351045 Timestamp [UCT]: 2026-01-02 10:50:45 Age [y:d:h:m:s]: 00:002:20:07:33
Block: 1446989 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 2028 RingCT/type: yes/0
Extra: 013f35cdfde2ebcd276be5fcbeb97255f8e0216c2d066f743b9167e2ed0c235beb021100000004215bbf89000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: b9545df743668e0ca7b450857f72befa002fb841251acb47583adadec0584d73 0.600000000000 1935947 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": 1446999, "vin": [ { "gen": { "height": 1446989 } } ], "vout": [ { "amount": 600000000, "target": { "key": "b9545df743668e0ca7b450857f72befa002fb841251acb47583adadec0584d73" } } ], "extra": [ 1, 63, 53, 205, 253, 226, 235, 205, 39, 107, 229, 252, 190, 185, 114, 85, 248, 224, 33, 108, 45, 6, 111, 116, 59, 145, 103, 226, 237, 12, 35, 91, 235, 2, 17, 0, 0, 0, 4, 33, 91, 191, 137, 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