Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 4c5f1910d9c0f102503a51bd9952ac1dabfc66b64007cf9f9ca2fed6b77d78a4

Tx prefix hash: 28e9822247229920be21b435a5f4ae99d66a7b95840db21c0c346cb36eb114d1
Tx public key: 537795bfa9c80e8cafaefd68aa86811a7615296d205955ed312cbc9f85e3e228
Timestamp: 1730636587 Timestamp [UCT]: 2024-11-03 12:23:07 Age [y:d:h:m:s]: 00:078:23:57:00
Block: 1145661 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 56475 RingCT/type: yes/0
Extra: 01537795bfa9c80e8cafaefd68aa86811a7615296d205955ed312cbc9f85e3e2280211000000021f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: a064d934251943e8d6fd7eb522a17e1b5b473a6a153ae724ec785a57adcba442 0.600000000000 1630148 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": 1145671, "vin": [ { "gen": { "height": 1145661 } } ], "vout": [ { "amount": 600000000, "target": { "key": "a064d934251943e8d6fd7eb522a17e1b5b473a6a153ae724ec785a57adcba442" } } ], "extra": [ 1, 83, 119, 149, 191, 169, 200, 14, 140, 175, 174, 253, 104, 170, 134, 129, 26, 118, 21, 41, 109, 32, 89, 85, 237, 49, 44, 188, 159, 133, 227, 226, 40, 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