Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: a6e07c21e4e7ef8c4ba9c581d5e34f9889b8ca38bc23ee714cf70936dbeae2c6

Tx prefix hash: 4a32e9c4e9b8f07751e8460f3b82206eee9dc2118f506ddd98bb80d8c8d75c13
Tx public key: 5554cda0f899d773414365a093240986bf0b85298498aa32267dfb9543201266
Timestamp: 1713931429 Timestamp [UCT]: 2024-04-24 04:03:49 Age [y:d:h:m:s]: 00:205:07:47:29
Block: 1007244 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 146979 RingCT/type: yes/0
Extra: 015554cda0f899d773414365a093240986bf0b85298498aa32267dfb954320126602110000000459dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 7b9870bcfd1c328f8f1913c7dd4d54621004c08363f39bb26c2d4b1dbd2b88f8 0.600000000000 1468522 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": 1007254, "vin": [ { "gen": { "height": 1007244 } } ], "vout": [ { "amount": 600000000, "target": { "key": "7b9870bcfd1c328f8f1913c7dd4d54621004c08363f39bb26c2d4b1dbd2b88f8" } } ], "extra": [ 1, 85, 84, 205, 160, 248, 153, 215, 115, 65, 67, 101, 160, 147, 36, 9, 134, 191, 11, 133, 41, 132, 152, 170, 50, 38, 125, 251, 149, 67, 32, 18, 102, 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