Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: ce7856b67c5b1252e49c968d07c360c6fe656ba6bd148d5e28de60f948eab7b2

Tx prefix hash: 460bd3ca19f9733cc6ffd473b0d40d0b09d99be99ceccf229b1bf0e69ee30650
Tx public key: 6b86eddefe6c3e7fd0df21ad536ab107b8d480136f2fa9a3027869b6aee619cc
Timestamp: 1740297423 Timestamp [UCT]: 2025-02-23 07:57:03 Age [y:d:h:m:s]: 00:278:02:05:19
Block: 1225354 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 196541 RingCT/type: yes/0
Extra: 016b86eddefe6c3e7fd0df21ad536ab107b8d480136f2fa9a3027869b6aee619cc021100000001a11dba98000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: c7ef15dfb5ce9479279c52094f2abcde9303e14f37e7ccc2e9acb2aeb6f0531c 0.600000000000 1712219 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": 1225364, "vin": [ { "gen": { "height": 1225354 } } ], "vout": [ { "amount": 600000000, "target": { "key": "c7ef15dfb5ce9479279c52094f2abcde9303e14f37e7ccc2e9acb2aeb6f0531c" } } ], "extra": [ 1, 107, 134, 237, 222, 254, 108, 62, 127, 208, 223, 33, 173, 83, 106, 177, 7, 184, 212, 128, 19, 111, 47, 169, 163, 2, 120, 105, 182, 174, 230, 25, 204, 2, 17, 0, 0, 0, 1, 161, 29, 186, 152, 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