Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 802d14cbc4211b1720201380ad5dda3a2d53a2e2f1764daa9a8a34d054aab893

Tx prefix hash: 041f0c9f827195a47427dda72ae0fb4460bb11d12c8a72ae463138395c1665ca
Tx public key: 0647149de292bd753e27c0181812eeb0cd6d2a5c1a3dc3acb4ee8289c45c4801
Timestamp: 1705406052 Timestamp [UCT]: 2024-01-16 11:54:12 Age [y:d:h:m:s]: 01:350:18:06:26
Block: 936546 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 509573 RingCT/type: yes/0
Extra: 010647149de292bd753e27c0181812eeb0cd6d2a5c1a3dc3acb4ee8289c45c480102110000000959dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 76e4dd40aeaa658aacbb6f16b3199fc9c65b66198c6918e25dc2102875b260a8 0.600000000000 1394574 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": 936556, "vin": [ { "gen": { "height": 936546 } } ], "vout": [ { "amount": 600000000, "target": { "key": "76e4dd40aeaa658aacbb6f16b3199fc9c65b66198c6918e25dc2102875b260a8" } } ], "extra": [ 1, 6, 71, 20, 157, 226, 146, 189, 117, 62, 39, 192, 24, 24, 18, 238, 176, 205, 109, 42, 92, 26, 61, 195, 172, 180, 238, 130, 137, 196, 92, 72, 1, 2, 17, 0, 0, 0, 9, 89, 218, 211, 245, 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