Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 4b3465de41f24f0701a490a79e8979477fb4e1238fc4ffec6147bb7c9a09603b

Tx prefix hash: 43a9b1ab9fb99ab54a7dace81c61798dc3ba42a33eaa01062e18d95d4b8438ec
Tx public key: b766688be557c011c6fe8d1d1f421c92e0f9266711143b151c3a79e6746689ec
Timestamp: 1704682758 Timestamp [UCT]: 2024-01-08 02:59:18 Age [y:d:h:m:s]: 01:155:01:57:04
Block: 930541 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 371990 RingCT/type: yes/0
Extra: 01b766688be557c011c6fe8d1d1f421c92e0f9266711143b151c3a79e6746689ec0211000000017a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: a69a3a743c08d9c6d8e3f5de7f4d2e2620d5d4f94bd65c3f71e32398f915716b 0.600000000000 1388423 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": 930551, "vin": [ { "gen": { "height": 930541 } } ], "vout": [ { "amount": 600000000, "target": { "key": "a69a3a743c08d9c6d8e3f5de7f4d2e2620d5d4f94bd65c3f71e32398f915716b" } } ], "extra": [ 1, 183, 102, 104, 139, 229, 87, 192, 17, 198, 254, 141, 29, 31, 66, 28, 146, 224, 249, 38, 103, 17, 20, 59, 21, 28, 58, 121, 230, 116, 102, 137, 236, 2, 17, 0, 0, 0, 1, 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