Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 2156cc6d171eb7c8740918ed6bcbc7f0de9d001f4327a55170220f80fea080e8

Tx prefix hash: 4827c074b74fcd97c0a29424af48940d638103d6f0e55482e02ad888577aa86f
Tx public key: 19b7c2c4d6696a691a35e32a26d9b51ce87d2969266a9b4c3fbf0dab282bee2c
Timestamp: 1707460113 Timestamp [UCT]: 2024-02-09 06:28:33 Age [y:d:h:m:s]: 00:223:09:59:24
Block: 953585 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 160040 RingCT/type: yes/0
Extra: 0119b7c2c4d6696a691a35e32a26d9b51ce87d2969266a9b4c3fbf0dab282bee2c02110000000359dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: acb206c814d955e1ce8b47517a2564ee6e667257cf375c588f3aa9cce2739c64 0.600000000000 1412817 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": 953595, "vin": [ { "gen": { "height": 953585 } } ], "vout": [ { "amount": 600000000, "target": { "key": "acb206c814d955e1ce8b47517a2564ee6e667257cf375c588f3aa9cce2739c64" } } ], "extra": [ 1, 25, 183, 194, 196, 214, 105, 106, 105, 26, 53, 227, 42, 38, 217, 181, 28, 232, 125, 41, 105, 38, 106, 155, 76, 63, 191, 13, 171, 40, 43, 238, 44, 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