Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 4f9829f67fea855bc2db8999bdbf3c5154335c500185f7648438240210f714b2

Tx prefix hash: bdb6975bd8074aaac71c397ae09a6eb4bab45c326633a01aeac8aae2cfceafac
Tx public key: ebbf6ecf6baf417296e0b963f2a3d9a030bb3c9ae8c12971f188a1d371dfd1b5
Timestamp: 1697203046 Timestamp [UCT]: 2023-10-13 13:17:26 Age [y:d:h:m:s]: 01:102:07:29:49
Block: 868756 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 334341 RingCT/type: yes/0
Extra: 01ebbf6ecf6baf417296e0b963f2a3d9a030bb3c9ae8c12971f188a1d371dfd1b5021100000008e6d27f9c000000000000000000

1 output(s) for total of 0.811803208000 dcy

stealth address amount amount idx
00: 0a7da00ba90a1eb97e2f2b51b7dae848ed98f1938f2da7f5c69ecd6727e1cc3e 0.811803208000 1323575 of 0

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": 868766, "vin": [ { "gen": { "height": 868756 } } ], "vout": [ { "amount": 811803208, "target": { "key": "0a7da00ba90a1eb97e2f2b51b7dae848ed98f1938f2da7f5c69ecd6727e1cc3e" } } ], "extra": [ 1, 235, 191, 110, 207, 107, 175, 65, 114, 150, 224, 185, 99, 242, 163, 217, 160, 48, 187, 60, 154, 232, 193, 41, 113, 241, 136, 161, 211, 113, 223, 209, 181, 2, 17, 0, 0, 0, 8, 230, 210, 127, 156, 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