Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 985f3499423a02187da34d7fa928685fe6b780bc151bf1e74a397fb2e865c0a6

Tx prefix hash: 5e6afb65735a2f6f382a89acb6d770cf5bf46084153aaabfb2229ac9905b5a8e
Tx public key: 1477f2653d96f49cad2b639b494023bf8a3e3a9621d9a46b066c2b209ee3dcff
Timestamp: 1706549443 Timestamp [UCT]: 2024-01-29 17:30:43 Age [y:d:h:m:s]: 01:133:05:02:42
Block: 946025 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 356331 RingCT/type: yes/0
Extra: 011477f2653d96f49cad2b639b494023bf8a3e3a9621d9a46b066c2b209ee3dcff02110000000359dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 57117564889b9920b4ff01451a8f38c15a7ac9a38d4efa15540314efa918cfb6 0.600000000000 1404355 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": 946035, "vin": [ { "gen": { "height": 946025 } } ], "vout": [ { "amount": 600000000, "target": { "key": "57117564889b9920b4ff01451a8f38c15a7ac9a38d4efa15540314efa918cfb6" } } ], "extra": [ 1, 20, 119, 242, 101, 61, 150, 244, 156, 173, 43, 99, 155, 73, 64, 35, 191, 138, 62, 58, 150, 33, 217, 164, 107, 6, 108, 43, 32, 158, 227, 220, 255, 2, 17, 0, 0, 0, 3, 89, 218, 211, 245, 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