Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: b5aa1f7dfdaf2b028486d47d28756ad413af50d59ab460c04c2e7a118db5402e

Tx prefix hash: 58ab13326b4fbd7c558e868346196a04e47a7889e48eb2ce681081fcf0c3a8e0
Tx public key: dd0f4e8c2beea9258564d307a1f2ac40ab3fe10ee2a8c3735fc154c17435ddbb
Timestamp: 1711392467 Timestamp [UCT]: 2024-03-25 18:47:47 Age [y:d:h:m:s]: 01:042:11:56:31
Block: 986219 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 291335 RingCT/type: yes/0
Extra: 01dd0f4e8c2beea9258564d307a1f2ac40ab3fe10ee2a8c3735fc154c17435ddbb02110000000341ee1c9b000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 00f64a04d2f2acc7dd6ef4cf953c15e46ff25b457503c2976305733575506783 0.600000000000 1446448 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": 986229, "vin": [ { "gen": { "height": 986219 } } ], "vout": [ { "amount": 600000000, "target": { "key": "00f64a04d2f2acc7dd6ef4cf953c15e46ff25b457503c2976305733575506783" } } ], "extra": [ 1, 221, 15, 78, 140, 43, 238, 169, 37, 133, 100, 211, 7, 161, 242, 172, 64, 171, 63, 225, 14, 226, 168, 195, 115, 95, 193, 84, 193, 116, 53, 221, 187, 2, 17, 0, 0, 0, 3, 65, 238, 28, 155, 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