Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: f831e1f047f3a3c3dc9284823b9c257792273517c59c7ebfe0abbc6d2dfc5ce7

Tx prefix hash: cf4e1fdc6f40f7ea904ee7609532828f020c12caf63033c8d56fa1501460e26a
Tx public key: e6a720805fde07c47e79ee83487e884e93500dc2bd38547564c506b8261cb4ad
Timestamp: 1703245994 Timestamp [UCT]: 2023-12-22 11:53:14 Age [y:d:h:m:s]: 01:136:12:13:06
Block: 918660 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 358699 RingCT/type: yes/0
Extra: 01e6a720805fde07c47e79ee83487e884e93500dc2bd38547564c506b8261cb4ad0211000000057a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 5866d3cee3d0b2d1a3d7eb501a2c8248795cda8043941cf5980c3ef501dfc7f7 0.600000000000 1376312 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": 918670, "vin": [ { "gen": { "height": 918660 } } ], "vout": [ { "amount": 600000000, "target": { "key": "5866d3cee3d0b2d1a3d7eb501a2c8248795cda8043941cf5980c3ef501dfc7f7" } } ], "extra": [ 1, 230, 167, 32, 128, 95, 222, 7, 196, 126, 121, 238, 131, 72, 126, 136, 78, 147, 80, 13, 194, 189, 56, 84, 117, 100, 197, 6, 184, 38, 28, 180, 173, 2, 17, 0, 0, 0, 5, 122, 156, 244, 199, 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