Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 8a52f6085c73fd0f4efcf4cf742700a5461f7349e1d11197463b0045b9efad35

Tx prefix hash: 632d798baeeed16c06d35afcab1dc621878c144fcf9463d3028ad93541e2ee03
Tx public key: 3d99a32d93eb50eb779a32c7eff66c2f07e968eecb42b3edc66a7c2c0c8ca63c
Timestamp: 1707808674 Timestamp [UCT]: 2024-02-13 07:17:54 Age [y:d:h:m:s]: 01:078:02:47:57
Block: 956473 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 316885 RingCT/type: yes/0
Extra: 013d99a32d93eb50eb779a32c7eff66c2f07e968eecb42b3edc66a7c2c0c8ca63c02110000000152d47e94000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 2e1f703d0f10a352a119b2b08c6ab23046c89224047da259b90ed14599101ac0 0.600000000000 1415781 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": 956483, "vin": [ { "gen": { "height": 956473 } } ], "vout": [ { "amount": 600000000, "target": { "key": "2e1f703d0f10a352a119b2b08c6ab23046c89224047da259b90ed14599101ac0" } } ], "extra": [ 1, 61, 153, 163, 45, 147, 235, 80, 235, 119, 154, 50, 199, 239, 246, 108, 47, 7, 233, 104, 238, 203, 66, 179, 237, 198, 106, 124, 44, 12, 140, 166, 60, 2, 17, 0, 0, 0, 1, 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