Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: e44c3a32efc596a3dd4022995e33986c0c2512b8d7d2a2e9078f1adecf6de795

Tx prefix hash: e9c713eb89db5c7583ad13129643f8d4a8ff4b4118662d51f086e51a1c95d5c9
Tx public key: c81ef511c3f2ac03847f55e5b4b487aafd0629842ffccad1c373213496e8e1e5
Timestamp: 1699676395 Timestamp [UCT]: 2023-11-11 04:19:55 Age [y:d:h:m:s]: 01:139:13:59:50
Block: 889061 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 360949 RingCT/type: yes/0
Extra: 01c81ef511c3f2ac03847f55e5b4b487aafd0629842ffccad1c373213496e8e1e5021100000004faf35c9c000000000000000000

1 output(s) for total of 0.695299376000 dcy

stealth address amount amount idx
00: cc69b53e27246ee4195916eb9fe1a0c0701c3ad9b0994e4f07a9ae714ad3a594 0.695299376000 1345038 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": 889071, "vin": [ { "gen": { "height": 889061 } } ], "vout": [ { "amount": 695299376, "target": { "key": "cc69b53e27246ee4195916eb9fe1a0c0701c3ad9b0994e4f07a9ae714ad3a594" } } ], "extra": [ 1, 200, 30, 245, 17, 195, 242, 172, 3, 132, 127, 85, 229, 180, 180, 135, 170, 253, 6, 41, 132, 47, 252, 202, 209, 195, 115, 33, 52, 150, 232, 225, 229, 2, 17, 0, 0, 0, 4, 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