Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 80df385cdde5f234e27667eb8435442581b0988c0c6ad5eef8a94d110f39fc01

Tx prefix hash: 53199abf818388692759374735fade6756e3c55d5f633cf4b4b56d6ecfd82e52
Tx public key: 84c270e9dd51d1a0af6be515f282d4f199541f607ccd9ce6b772ade2f40dd1c9
Timestamp: 1634819470 Timestamp [UCT]: 2021-10-21 12:31:10 Age [y:d:h:m:s]: 03:238:14:51:44
Block: 357435 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 948543 RingCT/type: yes/0
Extra: 0184c270e9dd51d1a0af6be515f282d4f199541f607ccd9ce6b772ade2f40dd1c90211000000123fc41461000000000000000000

1 output(s) for total of 40.148551331000 dcy

stealth address amount amount idx
00: 7612f2ce8daaad4ab5b27aab6156b4668b5e1c38d5c89e2f906f96cf1dfccac4 40.148551331000 728851 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": 357445, "vin": [ { "gen": { "height": 357435 } } ], "vout": [ { "amount": 40148551331, "target": { "key": "7612f2ce8daaad4ab5b27aab6156b4668b5e1c38d5c89e2f906f96cf1dfccac4" } } ], "extra": [ 1, 132, 194, 112, 233, 221, 81, 209, 160, 175, 107, 229, 21, 242, 130, 212, 241, 153, 84, 31, 96, 124, 205, 156, 230, 183, 114, 173, 226, 244, 13, 209, 201, 2, 17, 0, 0, 0, 18, 63, 196, 20, 97, 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