Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 6ed10e1f761dc4570864fa93df950130cb335d81a0514b205a9c92872e7966c5

Tx prefix hash: afc88142748bff7d082d2a7e855a8cc99c32263cc40b5c3a9dcabd071ca776b1
Tx public key: c954b8d65cc954791757f1c27c32e935a55bc1e833718f551231f51738ac77f7
Timestamp: 1649069801 Timestamp [UCT]: 2022-04-04 10:56:41 Age [y:d:h:m:s]: 02:344:09:13:24
Block: 472950 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 765687 RingCT/type: yes/0
Extra: 01c954b8d65cc954791757f1c27c32e935a55bc1e833718f551231f51738ac77f70211000000044da16a3a000000000000000000

1 output(s) for total of 16.631084275000 dcy

stealth address amount amount idx
00: e6086b8c67013391abb46f309fda98e623a86f9f667b8b83454cea95d83d453d 16.631084275000 892663 of 0

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": 472960, "vin": [ { "gen": { "height": 472950 } } ], "vout": [ { "amount": 16631084275, "target": { "key": "e6086b8c67013391abb46f309fda98e623a86f9f667b8b83454cea95d83d453d" } } ], "extra": [ 1, 201, 84, 184, 214, 92, 201, 84, 121, 23, 87, 241, 194, 124, 50, 233, 53, 165, 91, 193, 232, 51, 113, 143, 85, 18, 49, 245, 23, 56, 172, 119, 247, 2, 17, 0, 0, 0, 4, 77, 161, 106, 58, 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