Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 833a5d0f96ef988bfb93415378ad6564c54c96713cb28e30128c640dad64ffe5

Tx prefix hash: e505d741eef16a2cd43e3924b675f6d97c1a26174e0ff12a72dd972a221eb1e5
Tx public key: fd0809d7ab32a496a981d63c60aa55a577de37e90ea1dd40f17d029a48a2a534
Timestamp: 1711957239 Timestamp [UCT]: 2024-04-01 07:40:39 Age [y:d:h:m:s]: 01:045:16:33:53
Block: 990840 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 293678 RingCT/type: yes/0
Extra: 01fd0809d7ab32a496a981d63c60aa55a577de37e90ea1dd40f17d029a48a2a53402110000000852d47e94000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 920ded27c155719595f8fafccb3e5b5f85d5a35ad0c4a30e386944ae7367241b 0.600000000000 1451170 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": 990850, "vin": [ { "gen": { "height": 990840 } } ], "vout": [ { "amount": 600000000, "target": { "key": "920ded27c155719595f8fafccb3e5b5f85d5a35ad0c4a30e386944ae7367241b" } } ], "extra": [ 1, 253, 8, 9, 215, 171, 50, 164, 150, 169, 129, 214, 60, 96, 170, 85, 165, 119, 222, 55, 233, 14, 161, 221, 64, 241, 125, 2, 154, 72, 162, 165, 52, 2, 17, 0, 0, 0, 8, 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