Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: cf945fb4d78c09620695f87d526b1c6755abbbfff44f9a9d45384d0e2094a7be

Tx prefix hash: cf62401523085844840f65847f7fea242f9f8db96347ef5b71f3aca35add9738
Tx public key: 01669ab3b2def7e53593cd1f688bcf74fc89a1f31a40c472848eba5dbf5ea0ea
Timestamp: 1702933373 Timestamp [UCT]: 2023-12-18 21:02:53 Age [y:d:h:m:s]: 01:152:06:18:50
Block: 916062 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 369971 RingCT/type: yes/0
Extra: 0101669ab3b2def7e53593cd1f688bcf74fc89a1f31a40c472848eba5dbf5ea0ea021100000006e6d27f9c000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 9088bf6ba94ec72c446715f93c67f2576473e86429750e5a4d52bbd21d30b890 0.600000000000 1373536 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": 916072, "vin": [ { "gen": { "height": 916062 } } ], "vout": [ { "amount": 600000000, "target": { "key": "9088bf6ba94ec72c446715f93c67f2576473e86429750e5a4d52bbd21d30b890" } } ], "extra": [ 1, 1, 102, 154, 179, 178, 222, 247, 229, 53, 147, 205, 31, 104, 139, 207, 116, 252, 137, 161, 243, 26, 64, 196, 114, 132, 142, 186, 93, 191, 94, 160, 234, 2, 17, 0, 0, 0, 6, 230, 210, 127, 156, 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