Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: bfe0f11c51f3b826f72eed2ac30b2393472b5c51a69e662f06a57781d83ec1b8

Tx prefix hash: 82e0d81f0410fca1ffcc04e1080af90a2ed84cb628440a405c7fe156e545d564
Tx public key: a2490b790e9eb348193392eaacb7c0783c4857f3d0b89693799bd6b7a6d48bc8
Timestamp: 1710679330 Timestamp [UCT]: 2024-03-17 12:42:10 Age [y:d:h:m:s]: 01:030:01:44:14
Block: 980304 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 282469 RingCT/type: yes/0
Extra: 01a2490b790e9eb348193392eaacb7c0783c4857f3d0b89693799bd6b7a6d48bc802110000001c59dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 85ffa2a1a619191df6c19705be0c574adfe02f7aa088d0255c7fc3ac2ecba413 0.600000000000 1440369 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": 980314, "vin": [ { "gen": { "height": 980304 } } ], "vout": [ { "amount": 600000000, "target": { "key": "85ffa2a1a619191df6c19705be0c574adfe02f7aa088d0255c7fc3ac2ecba413" } } ], "extra": [ 1, 162, 73, 11, 121, 14, 158, 179, 72, 25, 51, 146, 234, 172, 183, 192, 120, 60, 72, 87, 243, 208, 184, 150, 147, 121, 155, 214, 183, 166, 212, 139, 200, 2, 17, 0, 0, 0, 28, 89, 218, 211, 245, 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