Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 40353333c513022f4ea5e9aa41bfd6283a06fb739acd8a05f562a40ff3ec4099

Tx prefix hash: 0f013204934703070c1dcf14c32c54735409e3355bc7a9ec37ad5b6850a7e3c2
Tx public key: 11b1e4661b8ecf72090f2fdae2c680957c2cd042b80c9655e83e53eea3c0a8a8
Timestamp: 1743163899 Timestamp [UCT]: 2025-03-28 12:11:39 Age [y:d:h:m:s]: 00:234:09:16:30
Block: 1249108 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 165251 RingCT/type: yes/0
Extra: 0111b1e4661b8ecf72090f2fdae2c680957c2cd042b80c9655e83e53eea3c0a8a80211000000021a970403000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: bc3a457edd6d275dcd1de7179624c724de47f33aadb6d6f63e554b007f857e2b 0.600000000000 1736143 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": 1249118, "vin": [ { "gen": { "height": 1249108 } } ], "vout": [ { "amount": 600000000, "target": { "key": "bc3a457edd6d275dcd1de7179624c724de47f33aadb6d6f63e554b007f857e2b" } } ], "extra": [ 1, 17, 177, 228, 102, 27, 142, 207, 114, 9, 15, 47, 218, 226, 198, 128, 149, 124, 44, 208, 66, 184, 12, 150, 85, 232, 62, 83, 238, 163, 192, 168, 168, 2, 17, 0, 0, 0, 2, 26, 151, 4, 3, 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