Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 7e435eecf4ead4a058f5e4855cbe50722bd31dde2f9c89d2b0fce7ecc8381f01

Tx prefix hash: b2d0c3ca4bca51cd53ce31a8eece9691511b18b954b067682b8593248d29a58f
Tx public key: caea4123e01f7be88bb12efa222f35baa8f5553b2ed3f6f1527faa436d317c0f
Timestamp: 1712385921 Timestamp [UCT]: 2024-04-06 06:45:21 Age [y:d:h:m:s]: 01:222:16:51:45
Block: 994402 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 417873 RingCT/type: yes/0
Extra: 01caea4123e01f7be88bb12efa222f35baa8f5553b2ed3f6f1527faa436d317c0f02110000000352d47e94000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 8ee807817fb2797b0b67d74afd8eb52f443f16a24b2ef3780f50da348fdb08ee 0.600000000000 1454804 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": 994412, "vin": [ { "gen": { "height": 994402 } } ], "vout": [ { "amount": 600000000, "target": { "key": "8ee807817fb2797b0b67d74afd8eb52f443f16a24b2ef3780f50da348fdb08ee" } } ], "extra": [ 1, 202, 234, 65, 35, 224, 31, 123, 232, 139, 177, 46, 250, 34, 47, 53, 186, 168, 245, 85, 59, 46, 211, 246, 241, 82, 127, 170, 67, 109, 49, 124, 15, 2, 17, 0, 0, 0, 3, 82, 212, 126, 148, 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