Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 1455449ea54538df7a2d742565902c0b3d920ec8d28bc7fe1ee27a84a6317987

Tx prefix hash: fe1c9685ed23f72d6a6022564edebf9a5342ad3ca5e9b529ef5be269a88c7ca3
Tx public key: 68a2ad1bee7b920e132b4f77f9d48cc45acb87e39aa65c06d1268f510fa08742
Timestamp: 1711711148 Timestamp [UCT]: 2024-03-29 11:19:08 Age [y:d:h:m:s]: 00:361:20:39:46
Block: 988853 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 258680 RingCT/type: yes/0
Extra: 0168a2ad1bee7b920e132b4f77f9d48cc45acb87e39aa65c06d1268f510fa087420211000000030011055b000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: b63bb9a0d314ff2449c725815daf75b0d4188f150a42fb3f1a607fa701247a77 0.600000000000 1449140 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": 988863, "vin": [ { "gen": { "height": 988853 } } ], "vout": [ { "amount": 600000000, "target": { "key": "b63bb9a0d314ff2449c725815daf75b0d4188f150a42fb3f1a607fa701247a77" } } ], "extra": [ 1, 104, 162, 173, 27, 238, 123, 146, 14, 19, 43, 79, 119, 249, 212, 140, 196, 90, 203, 135, 227, 154, 166, 92, 6, 209, 38, 143, 81, 15, 160, 135, 66, 2, 17, 0, 0, 0, 3, 0, 17, 5, 91, 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