Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: a3473eab8acd74f114d252c00014bb5c17acfed841c996e77ab64dd18659f25e

Tx prefix hash: 1cf008d5211e29c430ffdf25f6fbfa7e29654213cbd8aca35a80e6cfa7263352
Tx public key: 11e9526d8b4828741c0dc495bbd5ba68cc8b4fcfc86f9c20171587ce7fde76ed
Timestamp: 1698363124 Timestamp [UCT]: 2023-10-26 23:32:04 Age [y:d:h:m:s]: 01:233:06:34:45
Block: 878395 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 427657 RingCT/type: yes/0
Extra: 0111e9526d8b4828741c0dc495bbd5ba68cc8b4fcfc86f9c20171587ce7fde76ed0211000000034b8f5122000000000000000000

1 output(s) for total of 0.754245523000 dcy

stealth address amount amount idx
00: af79b2c38e221e0d636f179ae21f215a33eaac4165d257f79774a8b64d7d8e57 0.754245523000 1333835 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": 878405, "vin": [ { "gen": { "height": 878395 } } ], "vout": [ { "amount": 754245523, "target": { "key": "af79b2c38e221e0d636f179ae21f215a33eaac4165d257f79774a8b64d7d8e57" } } ], "extra": [ 1, 17, 233, 82, 109, 139, 72, 40, 116, 28, 13, 196, 149, 187, 213, 186, 104, 204, 139, 79, 207, 200, 111, 156, 32, 23, 21, 135, 206, 127, 222, 118, 237, 2, 17, 0, 0, 0, 3, 75, 143, 81, 34, 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