Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 331992f37fdb22991fbcf4d18f0beeabf6c417a85b9d20ea3500b8cab54ebc64

Tx prefix hash: 90f5755e0adeb3bd7f1ad90ec2ada27e664e9228b6c8d923c886f6b1628e36f9
Tx public key: 4a8fe3bf972be183f353e1086b8e9641292ca7ee54fdba55c0758596207547c2
Timestamp: 1705122336 Timestamp [UCT]: 2024-01-13 05:05:36 Age [y:d:h:m:s]: 01:157:02:08:41
Block: 934191 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 373305 RingCT/type: yes/0
Extra: 014a8fe3bf972be183f353e1086b8e9641292ca7ee54fdba55c0758596207547c20211000000017a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 858d4a4f03e6d81da2886933b0008db0a7fba597874f171af9b792e0c54ea542 0.600000000000 1392179 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": 934201, "vin": [ { "gen": { "height": 934191 } } ], "vout": [ { "amount": 600000000, "target": { "key": "858d4a4f03e6d81da2886933b0008db0a7fba597874f171af9b792e0c54ea542" } } ], "extra": [ 1, 74, 143, 227, 191, 151, 43, 225, 131, 243, 83, 225, 8, 107, 142, 150, 65, 41, 44, 167, 238, 84, 253, 186, 85, 192, 117, 133, 150, 32, 117, 71, 194, 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