Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 88ffbd5ee026c757201a3176b2e920f394efcfffeb2a1c245a9a9bde0669a678

Tx prefix hash: f6211035ebee7b759df22068f22a57957e793064a38c6a9519a7eaab82e541e9
Tx public key: 0e32f6ea5a824db08536ab355fef4145fc0f33a910aae34272f4356b581748a4
Timestamp: 1704308989 Timestamp [UCT]: 2024-01-03 19:09:49 Age [y:d:h:m:s]: 01:332:19:18:17
Block: 927477 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 496691 RingCT/type: yes/0
Extra: 010e32f6ea5a824db08536ab355fef4145fc0f33a910aae34272f4356b581748a4021100000002bfa22221000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 25db8226eed721be014510485890aae6baaa8fd215ae5f18b08413a10d79d52a 0.600000000000 1385313 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": 927487, "vin": [ { "gen": { "height": 927477 } } ], "vout": [ { "amount": 600000000, "target": { "key": "25db8226eed721be014510485890aae6baaa8fd215ae5f18b08413a10d79d52a" } } ], "extra": [ 1, 14, 50, 246, 234, 90, 130, 77, 176, 133, 54, 171, 53, 95, 239, 65, 69, 252, 15, 51, 169, 16, 170, 227, 66, 114, 244, 53, 107, 88, 23, 72, 164, 2, 17, 0, 0, 0, 2, 191, 162, 34, 33, 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