Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 278e91384646b9e6dc60207b260c28ba4235607385fa904017b89990a1c33633

Tx prefix hash: 302b5f5f37953e390ed3540c84b7470abd3b9ecc16a6746f9d7cf3336c7736dc
Tx public key: f1afaa968fe5e911c59e12a8a0525ad54a88ea0bdb842f65566254af2e2776d4
Timestamp: 1636649096 Timestamp [UCT]: 2021-11-11 16:44:56 Age [y:d:h:m:s]: 03:046:21:27:07
Block: 372219 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 812124 RingCT/type: yes/0
Extra: 01f1afaa968fe5e911c59e12a8a0525ad54a88ea0bdb842f65566254af2e2776d402110000000c4f792ffd000000000000000000

1 output(s) for total of 35.866114333000 dcy

stealth address amount amount idx
00: ca7587734fe73b2338c1a9e48c6e206c5a9a68f1e166d3aa3b01ab54a2ce1ec9 35.866114333000 754059 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": 372229, "vin": [ { "gen": { "height": 372219 } } ], "vout": [ { "amount": 35866114333, "target": { "key": "ca7587734fe73b2338c1a9e48c6e206c5a9a68f1e166d3aa3b01ab54a2ce1ec9" } } ], "extra": [ 1, 241, 175, 170, 150, 143, 229, 233, 17, 197, 158, 18, 168, 160, 82, 90, 213, 74, 136, 234, 11, 219, 132, 47, 101, 86, 98, 84, 175, 46, 39, 118, 212, 2, 17, 0, 0, 0, 12, 79, 121, 47, 253, 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