Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: f18853820c00393cefe82021789a10ec1f76f8f1479743005b1e5227d66d5c35

Tx prefix hash: 1aabf830dc9ed146e636dbc00820b6951e4419706b5d3e29ee5e95bc374fd1f8
Tx public key: 1c8f4fcdfbe399f05c47900fe62f52e5a2bdc3cd66b8994c32d2fb848da9bc4f
Timestamp: 1706584123 Timestamp [UCT]: 2024-01-30 03:08:43 Age [y:d:h:m:s]: 01:278:11:02:08
Block: 946303 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 457810 RingCT/type: yes/0
Extra: 011c8f4fcdfbe399f05c47900fe62f52e5a2bdc3cd66b8994c32d2fb848da9bc4f0211000000017a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: e4f4f32ef000f6a994c0b7c7102e6b68761c63b26593c86c8721ac64f6ac0624 0.600000000000 1404635 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": 946313, "vin": [ { "gen": { "height": 946303 } } ], "vout": [ { "amount": 600000000, "target": { "key": "e4f4f32ef000f6a994c0b7c7102e6b68761c63b26593c86c8721ac64f6ac0624" } } ], "extra": [ 1, 28, 143, 79, 205, 251, 227, 153, 240, 92, 71, 144, 15, 230, 47, 82, 229, 162, 189, 195, 205, 102, 184, 153, 76, 50, 210, 251, 132, 141, 169, 188, 79, 2, 17, 0, 0, 0, 1, 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