Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: b91ad430392814183c790a9920c9117b1feeacf6a2f8f643d42896b88c75b234

Tx prefix hash: afb002a812fbeb4f62f21aedc61558dcc4fb38f99910f0af4f4b7147ec8ae1b6
Tx public key: 26f9c0874a2e75a6403d1445c9237af468644163b7970e5fda2beb8957382c56
Timestamp: 1712744630 Timestamp [UCT]: 2024-04-10 10:23:50 Age [y:d:h:m:s]: 01:018:04:50:04
Block: 997386 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 273995 RingCT/type: yes/0
Extra: 0126f9c0874a2e75a6403d1445c9237af468644163b7970e5fda2beb8957382c56021100000002e08532b6000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: daee913b1733c6bc1ceaa7d79e8939b14e2fc362022ab81f43cf704e7f427d20 0.600000000000 1457818 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": 997396, "vin": [ { "gen": { "height": 997386 } } ], "vout": [ { "amount": 600000000, "target": { "key": "daee913b1733c6bc1ceaa7d79e8939b14e2fc362022ab81f43cf704e7f427d20" } } ], "extra": [ 1, 38, 249, 192, 135, 74, 46, 117, 166, 64, 61, 20, 69, 201, 35, 122, 244, 104, 100, 65, 99, 183, 151, 14, 95, 218, 43, 235, 137, 87, 56, 44, 86, 2, 17, 0, 0, 0, 2, 224, 133, 50, 182, 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