Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 17ad9cf24096474f5a9085627dd00d9d25c524d847b3544521da2bffc7e905d7

Tx prefix hash: 5effda14f2d2ccffb32206fc41530e18acddbfaad077e14628fb6d5c9cd9fccc
Tx public key: c2b2c9f247b13c86c2448534a084753c0f3cf4e09cc761098ad9065730d30ec2
Timestamp: 1716003652 Timestamp [UCT]: 2024-05-18 03:40:52 Age [y:d:h:m:s]: 00:321:03:24:16
Block: 1024419 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 229546 RingCT/type: yes/0
Extra: 01c2b2c9f247b13c86c2448534a084753c0f3cf4e09cc761098ad9065730d30ec2021100000002e08532b6000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: b1a9ee4cfc1714ab94f98e808c03e242d8b959c53922847a99fa87f4d2f39acc 0.600000000000 1490158 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": 1024429, "vin": [ { "gen": { "height": 1024419 } } ], "vout": [ { "amount": 600000000, "target": { "key": "b1a9ee4cfc1714ab94f98e808c03e242d8b959c53922847a99fa87f4d2f39acc" } } ], "extra": [ 1, 194, 178, 201, 242, 71, 177, 60, 134, 194, 68, 133, 52, 160, 132, 117, 60, 15, 60, 244, 224, 156, 199, 97, 9, 138, 217, 6, 87, 48, 211, 14, 194, 2, 17, 0, 0, 0, 2, 224, 133, 50, 182, 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