Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: a0c4a3345333a13de202c3b9a0b7b18d714545d72f7f92304c3186ea0a1fea29

Tx prefix hash: 2326cb4f95aea3fb10ee0b576f45e89877e020f523dab28287072ad54ff0f7d1
Tx public key: bc5f7fbf5182ce875781156be15a8f90b58ce5c4594d54567b6591c3f57fdb7f
Timestamp: 1705341982 Timestamp [UCT]: 2024-01-15 18:06:22 Age [y:d:h:m:s]: 00:361:03:11:41
Block: 936013 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 258560 RingCT/type: yes/0
Extra: 01bc5f7fbf5182ce875781156be15a8f90b58ce5c4594d54567b6591c3f57fdb7f0211000000077a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 3c84ae7e2480a79376e8cd9f40ca55e8eea5b6bbd3c20d7018e8f97a6dd3bf96 0.600000000000 1394035 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": 936023, "vin": [ { "gen": { "height": 936013 } } ], "vout": [ { "amount": 600000000, "target": { "key": "3c84ae7e2480a79376e8cd9f40ca55e8eea5b6bbd3c20d7018e8f97a6dd3bf96" } } ], "extra": [ 1, 188, 95, 127, 191, 81, 130, 206, 135, 87, 129, 21, 107, 225, 90, 143, 144, 181, 140, 229, 196, 89, 77, 84, 86, 123, 101, 145, 195, 245, 127, 219, 127, 2, 17, 0, 0, 0, 7, 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