Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 7ca5f245dfb6202f20aa4d72dbb6e5e6905e59c537f7233902d971734e5b7e66

Tx prefix hash: bdda9ca37b8a0b74e45712894cd43bd5f1cee6d086f6759ab9981c67abdde4c0
Tx public key: 5ca418cd55d1b22e9d0bace8af5ac627fedd263e19231942b0719ed40ff7cb18
Timestamp: 1720649967 Timestamp [UCT]: 2024-07-10 22:19:27 Age [y:d:h:m:s]: 00:260:17:21:11
Block: 1062948 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 186265 RingCT/type: yes/0
Extra: 015ca418cd55d1b22e9d0bace8af5ac627fedd263e19231942b0719ed40ff7cb18021100000002e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: a01fe49bd99ef44e9683adf591e4c8ec70e965979b13a66a3c60b403f81bb26c 0.600000000000 1533459 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": 1062958, "vin": [ { "gen": { "height": 1062948 } } ], "vout": [ { "amount": 600000000, "target": { "key": "a01fe49bd99ef44e9683adf591e4c8ec70e965979b13a66a3c60b403f81bb26c" } } ], "extra": [ 1, 92, 164, 24, 205, 85, 209, 178, 46, 157, 11, 172, 232, 175, 90, 198, 39, 254, 221, 38, 62, 25, 35, 25, 66, 176, 113, 158, 212, 15, 247, 203, 24, 2, 17, 0, 0, 0, 2, 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