Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 43c98c365e9372fca3e72c20fa7a38096a921a833f6aa1bbde5e73a777a1498c

Tx prefix hash: 54cf870bf4301918b611fa866fbc40e2a7a2ff79cbb98894de0d0b76b1ef315f
Tx public key: bfa708901e87ceeaf629917a413bb93b15e68f9594ac8a8b0ce16fa6eb23e10a
Timestamp: 1681635613 Timestamp [UCT]: 2023-04-16 09:00:13 Age [y:d:h:m:s]: 01:271:20:22:12
Block: 739735 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 455790 RingCT/type: yes/0
Extra: 01bfa708901e87ceeaf629917a413bb93b15e68f9594ac8a8b0ce16fa6eb23e10a021100000002b3164c24000000000000000000

1 output(s) for total of 2.172456477000 dcy

stealth address amount amount idx
00: 833d87b68d93f95e7382b7b9313a3dca4c3094d40eb9e6eaf79c184ba9cb17ed 2.172456477000 1186604 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": 739745, "vin": [ { "gen": { "height": 739735 } } ], "vout": [ { "amount": 2172456477, "target": { "key": "833d87b68d93f95e7382b7b9313a3dca4c3094d40eb9e6eaf79c184ba9cb17ed" } } ], "extra": [ 1, 191, 167, 8, 144, 30, 135, 206, 234, 246, 41, 145, 122, 65, 59, 185, 59, 21, 230, 143, 149, 148, 172, 138, 139, 12, 225, 111, 166, 235, 35, 225, 10, 2, 17, 0, 0, 0, 2, 179, 22, 76, 36, 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