Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 201e54cb5dc8b000d88dca03a199054dff42e7380138c5e1435892bc28169041

Tx prefix hash: 281cde377475b58de46bba252dbba168e13a7080b00bc4334fb12aac528bdf26
Tx public key: d2a295627c5dadf4756f46840e50e315e3cf939e30882f4e67b8ae57b982bbda
Timestamp: 1694834860 Timestamp [UCT]: 2023-09-16 03:27:40 Age [y:d:h:m:s]: 01:206:04:57:33
Block: 849114 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 408466 RingCT/type: yes/0
Extra: 01d2a295627c5dadf4756f46840e50e315e3cf939e30882f4e67b8ae57b982bbda02110000000cfaf35c9c000000000000000000

1 output(s) for total of 0.943046032000 dcy

stealth address amount amount idx
00: e56669aa170578587b5ce4bca5854d01918a9eaee51eb3b72479d7e665d77fbb 0.943046032000 1302756 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": 849124, "vin": [ { "gen": { "height": 849114 } } ], "vout": [ { "amount": 943046032, "target": { "key": "e56669aa170578587b5ce4bca5854d01918a9eaee51eb3b72479d7e665d77fbb" } } ], "extra": [ 1, 210, 162, 149, 98, 124, 93, 173, 244, 117, 111, 70, 132, 14, 80, 227, 21, 227, 207, 147, 158, 48, 136, 47, 78, 103, 184, 174, 87, 185, 130, 187, 218, 2, 17, 0, 0, 0, 12, 250, 243, 92, 156, 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