Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 826cf4cb8fff7e9570736d2d5991241b583cd86c96364b5deca9e4cd273a903b

Tx prefix hash: fd23d0835136d54671029160a281f4dd10cb95f83ce3858f70bcca8ab76248f4
Tx public key: 80295b6f6ce766abf1a7822608b94296f25ae72e3a7cc67a5f75303aa4288270
Timestamp: 1712955515 Timestamp [UCT]: 2024-04-12 20:58:35 Age [y:d:h:m:s]: 00:318:21:17:22
Block: 999134 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 227972 RingCT/type: yes/0
Extra: 0180295b6f6ce766abf1a7822608b94296f25ae72e3a7cc67a5f75303aa42882700211000000017a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 87f23ca9ec9aac8eb5a5dfebf557acefc04e92065f7eef589edea31b585a6acd 0.600000000000 1459612 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": 999144, "vin": [ { "gen": { "height": 999134 } } ], "vout": [ { "amount": 600000000, "target": { "key": "87f23ca9ec9aac8eb5a5dfebf557acefc04e92065f7eef589edea31b585a6acd" } } ], "extra": [ 1, 128, 41, 91, 111, 108, 231, 102, 171, 241, 167, 130, 38, 8, 185, 66, 150, 242, 90, 231, 46, 58, 124, 198, 122, 95, 117, 48, 58, 164, 40, 130, 112, 2, 17, 0, 0, 0, 1, 122, 156, 244, 199, 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