Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 0b2ccba3a81a2cb43cd17bd21e2f89ec8a0c23ed13491dee890475d20d7f5377

Tx prefix hash: 1916e883aced8c00e4e2dd2c58c94f7cf1a702897307b29898066d17c3f6aceb
Tx public key: 9d82033cbadaf19ddebe1afbfa5958f26fe0f3cedd7a51ac72590e0035fe2d43
Timestamp: 1712556681 Timestamp [UCT]: 2024-04-08 06:11:21 Age [y:d:h:m:s]: 01:209:23:38:55
Block: 995816 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 408770 RingCT/type: yes/0
Extra: 019d82033cbadaf19ddebe1afbfa5958f26fe0f3cedd7a51ac72590e0035fe2d4302110000000a59dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: bb0225a38ea79ce9fb626381d52582299dfa5afe0fddf36f2a6a0d3a17fd35e0 0.600000000000 1456230 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": 995826, "vin": [ { "gen": { "height": 995816 } } ], "vout": [ { "amount": 600000000, "target": { "key": "bb0225a38ea79ce9fb626381d52582299dfa5afe0fddf36f2a6a0d3a17fd35e0" } } ], "extra": [ 1, 157, 130, 3, 60, 186, 218, 241, 157, 222, 190, 26, 251, 250, 89, 88, 242, 111, 224, 243, 206, 221, 122, 81, 172, 114, 89, 14, 0, 53, 254, 45, 67, 2, 17, 0, 0, 0, 10, 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