Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: adeaff45f70a49d877abed0f1b66b47567978149b7a135cb47501371a22cab52

Tx prefix hash: 2d62bdecf629af89c2f289f8884824b6545292569110e4867df9bc7bacd07fb7
Tx public key: 833fee0bb6f2479cff6f02035a0e2e8691c5e38ce26dc39413d7696f550b4e8f
Timestamp: 1724655920 Timestamp [UCT]: 2024-08-26 07:05:20 Age [y:d:h:m:s]: 00:275:20:49:01
Block: 1096143 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 197078 RingCT/type: yes/0
Extra: 01833fee0bb6f2479cff6f02035a0e2e8691c5e38ce26dc39413d7696f550b4e8f021100000003e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 4bd729bfdd587a6a78fdaef3f6191b3521161e71637e618e56c60d6b7376e2b9 0.600000000000 1571330 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": 1096153, "vin": [ { "gen": { "height": 1096143 } } ], "vout": [ { "amount": 600000000, "target": { "key": "4bd729bfdd587a6a78fdaef3f6191b3521161e71637e618e56c60d6b7376e2b9" } } ], "extra": [ 1, 131, 63, 238, 11, 182, 242, 71, 156, 255, 111, 2, 3, 90, 14, 46, 134, 145, 197, 227, 140, 226, 109, 195, 148, 19, 215, 105, 111, 85, 11, 78, 143, 2, 17, 0, 0, 0, 3, 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