Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: a34f0f69fa406b25696b62cc5331c5d9953af0875c82f5578f0b43ea17e91ad3

Tx prefix hash: 823aec349b5e624d82f2a599c9dfbadf3d506ed16f86726e791c6425f68226d9
Tx public key: e395d69bf0b17f5ce3517e6e4a86ab739359c4948442d3cdf3db5207fe030e61
Timestamp: 1736209573 Timestamp [UCT]: 2025-01-07 00:26:13 Age [y:d:h:m:s]: 00:161:18:05:08
Block: 1191797 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 115319 RingCT/type: yes/0
Extra: 01e395d69bf0b17f5ce3517e6e4a86ab739359c4948442d3cdf3db5207fe030e61021100000002007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 08ae91cd8bdd5257b7f0e2eb5e8e75f756e4c58575709e4f44d9d8fc414f8f59 0.600000000000 1678338 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": 1191807, "vin": [ { "gen": { "height": 1191797 } } ], "vout": [ { "amount": 600000000, "target": { "key": "08ae91cd8bdd5257b7f0e2eb5e8e75f756e4c58575709e4f44d9d8fc414f8f59" } } ], "extra": [ 1, 227, 149, 214, 155, 240, 177, 127, 92, 227, 81, 126, 110, 74, 134, 171, 115, 147, 89, 196, 148, 132, 66, 211, 205, 243, 219, 82, 7, 254, 3, 14, 97, 2, 17, 0, 0, 0, 2, 0, 127, 151, 138, 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