Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 58df94ec16cf2ca4b74a85b60a892c88ff73081c4318c79cdfab66547a7bfbe7

Tx prefix hash: 0a9dc9319cceace62ce2f000c740412af65b3cbcf2975b7150733b6827a1ba7b
Tx public key: 58ab0fb66cd95dc84f14335d26836a3d16d6cb226b719f11dee1525cc2279b0f
Timestamp: 1709643372 Timestamp [UCT]: 2024-03-05 12:56:12 Age [y:d:h:m:s]: 01:272:17:11:26
Block: 971703 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 453657 RingCT/type: yes/0
Extra: 0158ab0fb66cd95dc84f14335d26836a3d16d6cb226b719f11dee1525cc2279b0f02110000000452d47e94000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: f1f863fd84897d1c4743ab68e62d1cc12d0e3add05b705e46dae06c519af3f11 0.600000000000 1431604 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": 971713, "vin": [ { "gen": { "height": 971703 } } ], "vout": [ { "amount": 600000000, "target": { "key": "f1f863fd84897d1c4743ab68e62d1cc12d0e3add05b705e46dae06c519af3f11" } } ], "extra": [ 1, 88, 171, 15, 182, 108, 217, 93, 200, 79, 20, 51, 93, 38, 131, 106, 61, 22, 214, 203, 34, 107, 113, 159, 17, 222, 225, 82, 92, 194, 39, 155, 15, 2, 17, 0, 0, 0, 4, 82, 212, 126, 148, 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