Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: aaec1c63e9b9ab1b714e073314924cdeb837ff29614970d539233acba4a7d0ec

Tx prefix hash: 29488c2257288984acf5efc07954edced19c99b8b07dbfab6afcac8acb0ec75e
Tx public key: f8efab64e93969410b4de8b01931f9539f7a2430ce6be4de280190d74a6a221f
Timestamp: 1764548194 Timestamp [UCT]: 2025-12-01 00:16:34 Age [y:d:h:m:s]: 00:035:21:59:31
Block: 1423759 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 25728 RingCT/type: yes/0
Extra: 01f8efab64e93969410b4de8b01931f9539f7a2430ce6be4de280190d74a6a221f021100000004d6e19d7c000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 96a1a97479317bd2cf6cfd42cdefe529be9cfb8b0aac80e1d89cbca6e7eee928 0.600000000000 1912380 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": 1423769, "vin": [ { "gen": { "height": 1423759 } } ], "vout": [ { "amount": 600000000, "target": { "key": "96a1a97479317bd2cf6cfd42cdefe529be9cfb8b0aac80e1d89cbca6e7eee928" } } ], "extra": [ 1, 248, 239, 171, 100, 233, 57, 105, 65, 11, 77, 232, 176, 25, 49, 249, 83, 159, 122, 36, 48, 206, 107, 228, 222, 40, 1, 144, 215, 74, 106, 34, 31, 2, 17, 0, 0, 0, 4, 214, 225, 157, 124, 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