Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 556df040d7254c6c9fc928e4305beec52f28c591d27847093adef6e0ae9b8f7a

Tx prefix hash: d5352bb539019bc5f545817bb0b9af251fe05befe317f8009d0598924e187264
Tx public key: 7ed1c3a4664183c24625fa5f609dcaa7a8abab4365e80ecceb0a46c8f08e481b
Timestamp: 1699115801 Timestamp [UCT]: 2023-11-04 16:36:41 Age [y:d:h:m:s]: 01:159:09:38:54
Block: 884670 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 374878 RingCT/type: yes/0
Extra: 017ed1c3a4664183c24625fa5f609dcaa7a8abab4365e80ecceb0a46c8f08e481b021100000003faf35c9c000000000000000000

1 output(s) for total of 0.718987023000 dcy

stealth address amount amount idx
00: 8226e4d583f74a1a1fb6a3c07b9c9a5b3ce57e78f6d23dd38f11be6d6db5edf1 0.718987023000 1340417 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": 884680, "vin": [ { "gen": { "height": 884670 } } ], "vout": [ { "amount": 718987023, "target": { "key": "8226e4d583f74a1a1fb6a3c07b9c9a5b3ce57e78f6d23dd38f11be6d6db5edf1" } } ], "extra": [ 1, 126, 209, 195, 164, 102, 65, 131, 194, 70, 37, 250, 95, 96, 157, 202, 167, 168, 171, 171, 67, 101, 232, 14, 204, 235, 10, 70, 200, 240, 142, 72, 27, 2, 17, 0, 0, 0, 3, 250, 243, 92, 156, 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