Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 381a18b10808b134def65b96cf3278eb8af471eb9d57d9a5fe130d39631f1a5f

Tx prefix hash: 73c885cdd4885677880b12e18b1c6922e1ec31752cf27a3d614910d2bd17b7ac
Tx public key: ea7180e0c287958b3db47d408f0f9979a488b5671921e49ee9e315a4528944a6
Timestamp: 1699399121 Timestamp [UCT]: 2023-11-07 23:18:41 Age [y:d:h:m:s]: 01:065:05:31:54
Block: 886771 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 308026 RingCT/type: yes/0
Extra: 01ea7180e0c287958b3db47d408f0f9979a488b5671921e49ee9e315a4528944a602110000000875e3f0e9000000000000000000

1 output(s) for total of 0.707553956000 dcy

stealth address amount amount idx
00: 787f3ab2e20ca1020e60d1691cd64f39d6bfc8d2bc1adafeb4818224a8d5ece4 0.707553956000 1342614 of 0

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": 886781, "vin": [ { "gen": { "height": 886771 } } ], "vout": [ { "amount": 707553956, "target": { "key": "787f3ab2e20ca1020e60d1691cd64f39d6bfc8d2bc1adafeb4818224a8d5ece4" } } ], "extra": [ 1, 234, 113, 128, 224, 194, 135, 149, 139, 61, 180, 125, 64, 143, 15, 153, 121, 164, 136, 181, 103, 25, 33, 228, 158, 233, 227, 21, 164, 82, 137, 68, 166, 2, 17, 0, 0, 0, 8, 117, 227, 240, 233, 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