Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 1976d7f889b135411dc26b3ca1dd24215a39c84b90e4ef7e1c3e47b8499bd824

Tx prefix hash: 7b90e65b6081550b7d78cf4660c31a877c1947f218ea9d83d076064e5f629277
Tx public key: 19863f39454ff03351d6eb6e0dcea5b98a525f9251137e269cdd3b698b75a3aa
Timestamp: 1702361318 Timestamp [UCT]: 2023-12-12 06:08:38 Age [y:d:h:m:s]: 01:164:05:03:54
Block: 911321 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 378539 RingCT/type: yes/0
Extra: 0119863f39454ff03351d6eb6e0dcea5b98a525f9251137e269cdd3b698b75a3aa02110000000275e3f0e9000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: eae78702be5c25c0017dbe58f5548e6604f3e76657d5ae534f617a9aad1e9761 0.600000000000 1368502 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": 911331, "vin": [ { "gen": { "height": 911321 } } ], "vout": [ { "amount": 600000000, "target": { "key": "eae78702be5c25c0017dbe58f5548e6604f3e76657d5ae534f617a9aad1e9761" } } ], "extra": [ 1, 25, 134, 63, 57, 69, 79, 240, 51, 81, 214, 235, 110, 13, 206, 165, 185, 138, 82, 95, 146, 81, 19, 126, 38, 156, 221, 59, 105, 139, 117, 163, 170, 2, 17, 0, 0, 0, 2, 117, 227, 240, 233, 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