Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 4468eb3660b7cce104f176d22079ceb6e107a63b667fb8e45d7becc9fd950dcd

Tx prefix hash: 9f50954119312170e8f197f43af10d79d774c852cf694c523cca51a95ba4a9ec
Tx public key: 3a94b828cd7a3ab332563cfc0b5c6c1fdcb364e0d41ae04aeb0543129dca7dd9
Timestamp: 1716967069 Timestamp [UCT]: 2024-05-29 07:17:49 Age [y:d:h:m:s]: 01:163:08:52:24
Block: 1032411 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 375349 RingCT/type: yes/0
Extra: 013a94b828cd7a3ab332563cfc0b5c6c1fdcb364e0d41ae04aeb0543129dca7dd90211000000070011055b000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: f7d72faeeba01aa50f708ef37e28765d2512d5767c702cbe50fc1ed9e3c96fbd 0.600000000000 1500864 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": 1032421, "vin": [ { "gen": { "height": 1032411 } } ], "vout": [ { "amount": 600000000, "target": { "key": "f7d72faeeba01aa50f708ef37e28765d2512d5767c702cbe50fc1ed9e3c96fbd" } } ], "extra": [ 1, 58, 148, 184, 40, 205, 122, 58, 179, 50, 86, 60, 252, 11, 92, 108, 31, 220, 179, 100, 224, 212, 26, 224, 74, 235, 5, 67, 18, 157, 202, 125, 217, 2, 17, 0, 0, 0, 7, 0, 17, 5, 91, 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