Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: b83ecce98e51863f43efa4ea3f420ae87f9cd7af47396ecb37ba80d4eb9f01fa

Tx prefix hash: 7ca01fd04a058c01f085f4f912c7e27377582d13f7cd8e1ceb5e1d28714b8cd9
Tx public key: 7951580a6447b31fc811acfd9ee87d9ba3211d297d2404b08b632b0f0c3b98f3
Timestamp: 1735303271 Timestamp [UCT]: 2024-12-27 12:41:11 Age [y:d:h:m:s]: 00:173:23:32:46
Block: 1184290 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 124044 RingCT/type: yes/0
Extra: 017951580a6447b31fc811acfd9ee87d9ba3211d297d2404b08b632b0f0c3b98f30211000000041f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: d05ffb3a0ae458f14bccf62c8a47dfa6e1b39bb326d9b842548c81d8b78c7448 0.600000000000 1670747 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": 1184300, "vin": [ { "gen": { "height": 1184290 } } ], "vout": [ { "amount": 600000000, "target": { "key": "d05ffb3a0ae458f14bccf62c8a47dfa6e1b39bb326d9b842548c81d8b78c7448" } } ], "extra": [ 1, 121, 81, 88, 10, 100, 71, 179, 31, 200, 17, 172, 253, 158, 232, 125, 155, 163, 33, 29, 41, 125, 36, 4, 176, 139, 99, 43, 15, 12, 59, 152, 243, 2, 17, 0, 0, 0, 4, 31, 10, 83, 235, 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