Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: cfa7733f55521b4a7c439a4b61a8f309f58dbbff67f41472e96181c696693b29

Tx prefix hash: 3f41bc29d4550115d0bf937095649e0cbec0feaad030eac20ca1bb72234fe452
Tx public key: 2d0e7638e8b35547705b9ab1ceb479f746b306897dff38d31dc369e6b7a88476
Timestamp: 1725375554 Timestamp [UCT]: 2024-09-03 14:59:14 Age [y:d:h:m:s]: 00:262:17:17:28
Block: 1102126 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 187650 RingCT/type: yes/0
Extra: 012d0e7638e8b35547705b9ab1ceb479f746b306897dff38d31dc369e6b7a88476021100000004e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: f70d37d6b2c6e1e309c13908fed3e6286b9bd6e4b96747b20d726f9bf3327a2b 0.600000000000 1578437 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": 1102136, "vin": [ { "gen": { "height": 1102126 } } ], "vout": [ { "amount": 600000000, "target": { "key": "f70d37d6b2c6e1e309c13908fed3e6286b9bd6e4b96747b20d726f9bf3327a2b" } } ], "extra": [ 1, 45, 14, 118, 56, 232, 179, 85, 71, 112, 91, 154, 177, 206, 180, 121, 247, 70, 179, 6, 137, 125, 255, 56, 211, 29, 195, 105, 230, 183, 168, 132, 118, 2, 17, 0, 0, 0, 4, 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