Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 14216fa14a7de916dcf45f4304229004853efb38e7a58702d9eabbb7b15e35b6

Tx prefix hash: 4262f935410bf0bd714daf75c89d9328ffb3cfe47967da83e2c0b69bab3c6654
Tx public key: bf1ddcdfc8f2a5d4297045601db77bf52d038c1f5718155a9bbff07bd912f9e2
Timestamp: 1736376368 Timestamp [UCT]: 2025-01-08 22:46:08 Age [y:d:h:m:s]: 00:119:05:26:30
Block: 1193187 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 85007 RingCT/type: yes/0
Extra: 01bf1ddcdfc8f2a5d4297045601db77bf52d038c1f5718155a9bbff07bd912f9e20211000000021f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 5274ba1fb2392533185ec6d8e7f3ae4d3ec27c1e2129e457ab3f8c11b91f5bb4 0.600000000000 1679746 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": 1193197, "vin": [ { "gen": { "height": 1193187 } } ], "vout": [ { "amount": 600000000, "target": { "key": "5274ba1fb2392533185ec6d8e7f3ae4d3ec27c1e2129e457ab3f8c11b91f5bb4" } } ], "extra": [ 1, 191, 29, 220, 223, 200, 242, 165, 212, 41, 112, 69, 96, 29, 183, 123, 245, 45, 3, 140, 31, 87, 24, 21, 90, 155, 191, 240, 123, 217, 18, 249, 226, 2, 17, 0, 0, 0, 2, 31, 10, 83, 235, 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