Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 38d44c3a739f48d5456c6eab4c65d90c97b6c40558354d99f23f100206719c33

Tx prefix hash: 8c2f02ae46e47317c2a249ec547aef767b780782f1bf98c1521b3fbaf3f85716
Tx public key: 9cc1e0d07f1a9b22a9a1d157d5dbb1628db011e5a893b4e8e8bb3f324d2f8ac5
Timestamp: 1713864005 Timestamp [UCT]: 2024-04-23 09:20:05 Age [y:d:h:m:s]: 00:354:03:46:36
Block: 1006681 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 253182 RingCT/type: yes/0
Extra: 019cc1e0d07f1a9b22a9a1d157d5dbb1628db011e5a893b4e8e8bb3f324d2f8ac50211000000027a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 954212415a1d6311ea006e0e2e6159300a068139150b335bbea53b7c57fddf50 0.600000000000 1467779 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": 1006691, "vin": [ { "gen": { "height": 1006681 } } ], "vout": [ { "amount": 600000000, "target": { "key": "954212415a1d6311ea006e0e2e6159300a068139150b335bbea53b7c57fddf50" } } ], "extra": [ 1, 156, 193, 224, 208, 127, 26, 155, 34, 169, 161, 209, 87, 213, 219, 177, 98, 141, 176, 17, 229, 168, 147, 180, 232, 232, 187, 63, 50, 77, 47, 138, 197, 2, 17, 0, 0, 0, 2, 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