Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: c029c1a261c9a61c222eff08d15174c8069c6cb6664b13f4eea2722ae5eb086b

Tx prefix hash: be6768764eb8920fce57a98b5c538f34b8f871a77aba93dd0d990fa9bcc76522
Tx public key: 03fd78043fba62118f63934c00f8e213d07b4624b716cd70bce397c8159bbb51
Timestamp: 1725304397 Timestamp [UCT]: 2024-09-02 19:13:17 Age [y:d:h:m:s]: 00:174:00:41:14
Block: 1101532 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 124185 RingCT/type: yes/0
Extra: 0103fd78043fba62118f63934c00f8e213d07b4624b716cd70bce397c8159bbb51021100000006e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: dc2f3d3b1b62199e8240e1b4d1dc6d10b7e521196fefb0e6b136272fb6e7575d 0.600000000000 1577619 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": 1101542, "vin": [ { "gen": { "height": 1101532 } } ], "vout": [ { "amount": 600000000, "target": { "key": "dc2f3d3b1b62199e8240e1b4d1dc6d10b7e521196fefb0e6b136272fb6e7575d" } } ], "extra": [ 1, 3, 253, 120, 4, 63, 186, 98, 17, 143, 99, 147, 76, 0, 248, 226, 19, 208, 123, 70, 36, 183, 22, 205, 112, 188, 227, 151, 200, 21, 155, 187, 81, 2, 17, 0, 0, 0, 6, 233, 20, 221, 21, 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