Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 0485023bc3b632f160503c0adae0475c53758c0219f97215ec303625034e6914

Tx prefix hash: 7dddf4244eaf5e1c8ad17c6e924ca2dc6234eb4ba7bf3d096c293f375b0f4138
Tx public key: dd2df1aaffd6cbe52de011a30d9cbe93ff7e20f301e155d7cfe80a9cd1ca8fa6
Timestamp: 1706082057 Timestamp [UCT]: 2024-01-24 07:40:57 Age [y:d:h:m:s]: 01:306:12:25:30
Block: 942138 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 477907 RingCT/type: yes/0
Extra: 01dd2df1aaffd6cbe52de011a30d9cbe93ff7e20f301e155d7cfe80a9cd1ca8fa60211000000057a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: a9642bd8dc40cba4670945430e0d2ad692a6360b0eb36cff8cf665d899acec78 0.600000000000 1400304 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": 942148, "vin": [ { "gen": { "height": 942138 } } ], "vout": [ { "amount": 600000000, "target": { "key": "a9642bd8dc40cba4670945430e0d2ad692a6360b0eb36cff8cf665d899acec78" } } ], "extra": [ 1, 221, 45, 241, 170, 255, 214, 203, 229, 45, 224, 17, 163, 13, 156, 190, 147, 255, 126, 32, 243, 1, 225, 85, 215, 207, 232, 10, 156, 209, 202, 143, 166, 2, 17, 0, 0, 0, 5, 122, 156, 244, 199, 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