Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 0d69cebb2adeac706cd08714b9fb02d0ef02276ced44108f1496a9c2f06de37a

Tx prefix hash: e9dbb037569ac1d4f2d190ef2258fe5b71fdf95d70a6be46c34e1e6e57fe6d17
Tx public key: a9d4c9ee1dcf239abedeec20fc0d9b43adca1fef0d5848c848ae7704c0fe992d
Timestamp: 1705590481 Timestamp [UCT]: 2024-01-18 15:08:01 Age [y:d:h:m:s]: 01:063:02:19:55
Block: 938077 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 306187 RingCT/type: yes/0
Extra: 01a9d4c9ee1dcf239abedeec20fc0d9b43adca1fef0d5848c848ae7704c0fe992d02110000000459dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: e91f6513ea9a53cdd6e00d251f70d12bf9ba1d4a1bf0bae172f79b1d9c2feaab 0.600000000000 1396141 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": 938087, "vin": [ { "gen": { "height": 938077 } } ], "vout": [ { "amount": 600000000, "target": { "key": "e91f6513ea9a53cdd6e00d251f70d12bf9ba1d4a1bf0bae172f79b1d9c2feaab" } } ], "extra": [ 1, 169, 212, 201, 238, 29, 207, 35, 154, 190, 222, 236, 32, 252, 13, 155, 67, 173, 202, 31, 239, 13, 88, 72, 200, 72, 174, 119, 4, 192, 254, 153, 45, 2, 17, 0, 0, 0, 4, 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