Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 2052deb8bd7fc28bacd90cd4f74c5534fe45154a90105ab329ae47a14f3b75ca

Tx prefix hash: 7f92b3e18547f1e3115ad9ed359026663ea919e417e1a2f424aed682dad6d665
Tx public key: dba95b2aee0b124bb0f7d64c215dc1602f25b5f21b48270c777e7b6f1b44ad63
Timestamp: 1721206074 Timestamp [UCT]: 2024-07-17 08:47:54 Age [y:d:h:m:s]: 00:257:11:11:43
Block: 1067568 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 183919 RingCT/type: yes/0
Extra: 01dba95b2aee0b124bb0f7d64c215dc1602f25b5f21b48270c777e7b6f1b44ad6302110000000f91e13c04000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 2b401652a4eb90ec1bbf9c75a3315157b519b1dd52f9a242ebdab37cc52d4619 0.600000000000 1538411 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": 1067578, "vin": [ { "gen": { "height": 1067568 } } ], "vout": [ { "amount": 600000000, "target": { "key": "2b401652a4eb90ec1bbf9c75a3315157b519b1dd52f9a242ebdab37cc52d4619" } } ], "extra": [ 1, 219, 169, 91, 42, 238, 11, 18, 75, 176, 247, 214, 76, 33, 93, 193, 96, 47, 37, 181, 242, 27, 72, 39, 12, 119, 126, 123, 111, 27, 68, 173, 99, 2, 17, 0, 0, 0, 15, 145, 225, 60, 4, 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