Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 002173e891c709709a79daca8dfb4ad2bf47573065dfa5cf76e5ac6e4144b327

Tx prefix hash: f3d9e454cc3c4a11f536b3ceb63fb6a556f6d877fa55a9d91edd5afc7b3328a0
Tx public key: 045f40f0186966b0d7ff6e2f983d618c3a2d66a8c43aa9d53510a623d3356e98
Timestamp: 1705360428 Timestamp [UCT]: 2024-01-15 23:13:48 Age [y:d:h:m:s]: 01:085:11:47:54
Block: 936168 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 322203 RingCT/type: yes/0
Extra: 01045f40f0186966b0d7ff6e2f983d618c3a2d66a8c43aa9d53510a623d3356e980211000000077a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 77a0db3701a248bcb49f760cab160ddab1385059aab9d5a6f15f0b6907af8655 0.600000000000 1394192 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": 936178, "vin": [ { "gen": { "height": 936168 } } ], "vout": [ { "amount": 600000000, "target": { "key": "77a0db3701a248bcb49f760cab160ddab1385059aab9d5a6f15f0b6907af8655" } } ], "extra": [ 1, 4, 95, 64, 240, 24, 105, 102, 176, 215, 255, 110, 47, 152, 61, 97, 140, 58, 45, 102, 168, 196, 58, 169, 213, 53, 16, 166, 35, 211, 53, 110, 152, 2, 17, 0, 0, 0, 7, 122, 156, 244, 199, 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