Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: f9f579e38d11ddb96bf0dba3488e0b52197dd0ddde3df972bd78a627043d9de5

Tx prefix hash: f8f90bb572c8ae31f7ae25b6b47d079cc2f696a1192f91aef888f15d583ff0bd
Tx public key: dc556bfce53d569f52544e54e4b6a95a43f678c79fee30bfc5c17b49fb473e33
Timestamp: 1723085456 Timestamp [UCT]: 2024-08-08 02:50:56 Age [y:d:h:m:s]: 01:093:01:14:52
Block: 1083139 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 324971 RingCT/type: yes/0
Extra: 01dc556bfce53d569f52544e54e4b6a95a43f678c79fee30bfc5c17b49fb473e33021100000006e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 15f30e2ae43f8808bc798f5d1679b7061534a838ca3436007e503728240631c2 0.600000000000 1556974 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": 1083149, "vin": [ { "gen": { "height": 1083139 } } ], "vout": [ { "amount": 600000000, "target": { "key": "15f30e2ae43f8808bc798f5d1679b7061534a838ca3436007e503728240631c2" } } ], "extra": [ 1, 220, 85, 107, 252, 229, 61, 86, 159, 82, 84, 78, 84, 228, 182, 169, 90, 67, 246, 120, 199, 159, 238, 48, 191, 197, 193, 123, 73, 251, 71, 62, 51, 2, 17, 0, 0, 0, 6, 233, 20, 221, 21, 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